You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a server implementing the graphql-ws protocol that is enforcing a JWT is present in the connection_init payload under connectionParams.token, as per enisdenjo/graphql-ws#263 .
In Apollo Studio I can add this token to the list of headers in the connection settings, with the expectation these are added to connectionParams sent with the subscription.
What I observe is two separate connection_init requests are made, one without the token and one with. If I reject the one without the token, the second connection_init request is not made, and the subscription fails. If I allow the first connection to occur (by returning connection_ack), the second one with the correct payload proceeds and the subscription succeeds.
I would expect a single connection_init request to be made with the headers present. The current behaviour means that a websocket API that requires authentication as part of connection_init is not useable from Apollo Studio.
The text was updated successfully, but these errors were encountered:
I have a server implementing the
graphql-ws
protocol that is enforcing a JWT is present in theconnection_init
payload underconnectionParams.token
, as per enisdenjo/graphql-ws#263 .In Apollo Studio I can add this token to the list of headers in the connection settings, with the expectation these are added to
connectionParams
sent with the subscription.What I observe is two separate
connection_init
requests are made, one without the token and one with. If I reject the one without the token, the secondconnection_init
request is not made, and the subscription fails. If I allow the first connection to occur (by returningconnection_ack
), the second one with the correct payload proceeds and the subscription succeeds.I would expect a single connection_init request to be made with the headers present. The current behaviour means that a websocket API that requires authentication as part of
connection_init
is not useable from Apollo Studio.The text was updated successfully, but these errors were encountered: