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.
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.