-
Notifications
You must be signed in to change notification settings - Fork 2.8k
close websocket connection on JWT expiry (fix #578) #2156
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
Conversation
Resolve Conflicts: server/src-lib/Hasura/GraphQL/Transport/WebSocket.hs
|
Deploy preview for hasura-docs ready! Built with commit 41506f9 |
|
Review app for commit be0b3e9 deployed to Heroku: https://hge-ci-pull-2156.herokuapp.com |
Explicitly return jwt expiry time while resolving user info
|
Review app for commit 936dff3 deployed to Heroku: https://hge-ci-pull-2156.herokuapp.com |
|
Review app for commit 3667311 deployed to Heroku: https://hge-ci-pull-2156.herokuapp.com |
|
Review app for commit 41506f9 deployed to Heroku: https://hge-ci-pull-2156.herokuapp.com |
|
Review app https://hge-ci-pull-2156.herokuapp.com is deleted |
Add `forward_headers` config to `pre-ndc-request-plugin` which allows request headers to be forwarded to `pre-ndc-request` plugins. V3_GIT_ORIGIN_REV_ID: 37035e9ff39716b6fead05275e0dc9633f351198
Description
Close WebSocket connection while subscriptions on JWT expiry.
Affected components
Related Issues
close #578
Solution and Design
Run an async thread on websocket connection accept which terminates on JWT expiry.
Steps to test and verify
Perform a subscription query with JWT setup. The server should close connection on JWT expiry.
Limitations, known bugs & workarounds