-
Notifications
You must be signed in to change notification settings - Fork 7
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
if upstream is down, authentication JWT is not cached #17
Comments
I think it's reasonable to cache (TOFU) the JWKS. |
Is probably not possible. We intentionally don't provide detailed error messages. It's considered a security leak. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
If a destination TCP upstream is down, Pomerium serves
HTTP 503
and JWT auth token would not be persisted by the CLI.That causes two issues:
What did you expect to happen?
The text was updated successfully, but these errors were encountered: