Skip to content
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

Refreshed token doesn't contain capabilities for all channels #55

Open
sacOO7 opened this issue Dec 5, 2024 · 2 comments · May be fixed by #56
Open

Refreshed token doesn't contain capabilities for all channels #55

sacOO7 opened this issue Dec 5, 2024 · 2 comments · May be fixed by #56
Assignees
Labels
bug Something isn't working. It's clear that this does need to be fixed.

Comments

@sacOO7
Copy link
Collaborator

sacOO7 commented Dec 5, 2024

  • Customer has reported an issue where refreshed token doesn't contain all channels, causing existing channels to reconnect again.

The current issue is that when Ably hits the token expiry time, it makes multiple token refresh calls. Although the current token has all the necessary capabilities, the server sometimes responds with a token containing only the channel_name provided in the payload. This causes the token to be marked as invalid, which then triggers another refresh cycle to obtain a token with proper capabilities.

┆Issue is synchronized with this Jira Bug by Unito

@sacOO7 sacOO7 self-assigned this Dec 5, 2024
@sacOO7 sacOO7 added the bug Something isn't working. It's clear that this does need to be fixed. label Dec 5, 2024
@sacOO7
Copy link
Collaborator Author

sacOO7 commented Dec 5, 2024

A temporary solution for now would be to set maximum ABLY_TOKEN_EXPIRY in .env file.

ABLY_TOKEN_EXPIRY= 86400  // 1 day ( 24 * 60 * 60 ) seconds

@sacOO7
Copy link
Collaborator Author

sacOO7 commented Dec 18, 2024

@sacOO7 sacOO7 linked a pull request Dec 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working. It's clear that this does need to be fixed.
Development

Successfully merging a pull request may close this issue.

1 participant