JWT auth + refresh token issue about graphql-subscriptions HOT 4 CLOSED

@DxCx I know, and we had a discussion about it few months ago.
It's hard to maintain authentication with refresh tokens when using WebSocket connection, because validating it in during the construction of the connection is not enough sometimes, and validating it every message is probably too heavy.

In the ws transport with have both onConnect and onOperation, and I think that each application should choose the best flow and solution for itself.

from graphql-subscriptions.

@akaNightmare
I think this issue is more related to subscriptions-transport-ws package.
Since version 0.7.0 of the transport, you can specify onOperation and add custom logic to verify your token, then return a new context when each operation is executed.
You can see an example for this in GitHunt server example: https://github.com/apollographql/GitHunt-API/blob/master/api/server.js#L160

from graphql-subscriptions.

@dotansimha websocket is not like http,
http will need to reconstruct the session every request, but on websocket
context can be constructed once on connect phase and then you can keep the session,
onOperation should just attach this session..

from graphql-subscriptions.

If you're still having problems with this, please reply below... not quite sure if this is the right place for this.

from graphql-subscriptions.