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
When a subscription is created a websocket is established. Under some circumstances (network disruption, VPN switching etc) a new websocket connection is established. But the authorization header is not updated. If the access token has since expired then Appsync will return:
[{errorType: "UnauthorizedException", message: "Token has expired."}]
What is the expected behavior?
The authorization header should use the token returned by the jwtToken function in the Appsync client config.
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Using the following config when creating a client:
When a subscription is created a websocket is established. Under some circumstances (network disruption, VPN switching etc) a new websocket connection is established. But the authorization header is not updated. If the access token has since expired then Appsync will return:
[{errorType: "UnauthorizedException", message: "Token has expired."}]
What is the expected behavior?
The authorization header should use the token returned by the
jwtToken
function in the Appsync client config.The text was updated successfully, but these errors were encountered: