Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Mercure] Explain if Caddy's publisher_jwt and subscriber_jwt should be the same or different #20378

Open
ThomasLandauer opened this issue Nov 8, 2024 · 0 comments
Labels

Comments

@ThomasLandauer
Copy link
Contributor

Ping @dunglas
Mercure's Caddyfile contains two keys: publisher_jwt and subscriber_jwt (by default populated through the environment variables $MERCURE_PUBLISHER_JWT_KEY and $MERCURE_SUBSCRIBER_JWT_KEY).
But the bundles's config/packages/mercure.yaml contains only one secret.
How does this fit together? Are people supposed to use the same string for both keys in the Caddyfile?

  • If yes, then why do two settings exist? And isn't this a security risk (kindof allowing subscribers to publish)?
  • If no, then how to pass the two strings to the bundle?
@ThomasLandauer ThomasLandauer changed the title [MercureBundle] Explain if the Caddy's publisher_jwt and subscriber_jwt should be the same or different [MercureBundle] Explain if Caddy's publisher_jwt and subscriber_jwt should be the same or different Nov 8, 2024
@xabbuh xabbuh added the Mercure label Nov 8, 2024
@ThomasLandauer ThomasLandauer changed the title [MercureBundle] Explain if Caddy's publisher_jwt and subscriber_jwt should be the same or different [Mercure] Explain if Caddy's publisher_jwt and subscriber_jwt should be the same or different Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants