-
Notifications
You must be signed in to change notification settings - Fork 187
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
Wait loop when using JWKS #634
Comments
This can also happen on |
second that.
my docker images are: image: hasura/graphql-engine:v2.0.3.cli-migrations-v3
image: nhost/hasura-backend-plus:latest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using JWKS hasura-backend-plus will wait with starting until hasura (graphql-engine) is ready. But graphql-engine will never become ready because it will wait for the JWKS endpoint of hasura-backend-plus to become ready first.
To Reproduce
Steps to reproduce the behavior:
HASURA_GRAPHQL_JWT_SECRET: '{"type": "RS256", "jwk_url": "http:https://hasura-backend-plus:3000/auth/jwks"}'
Expected behavior
The hasura-backend-plus application should expose JWKS endpoint on app startup even if Hasura is not ready
Additional context
hasura-backend-plus
2.6.1
works fine, JWKS api is broken in2.7.1
The text was updated successfully, but these errors were encountered: