-
Notifications
You must be signed in to change notification settings - Fork 10
Open
Labels
Description
Support Cross tab RT token usage better
Problem
When you use a micro-front end and store your refresh tokens in cookies, refreshing can happen from multiple JS requests, causing issues. In particular, if you have one time use tokens, this scenario can happen:
- JS in component 1 refreshes access token, gets RT A as well
- JS in component 2 refreshes access token, gets RT B and invalidates RT A
Multiply by many possible components, and you get a thundering herd of RT requests.
Solution
The JS client should handle RT management across tabs.
Alternatives/workarounds
Handle the token management in client side code.
Additional context
Related Issues:
- Allow for single use refresh token to be successful during mulitple refresh requuests in short window (reuser internal) fusionauth-issues#2867
- The client libraries should include token management functionality fusionauth-issues#1674
Internal:
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.
How to vote
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
Reactions are currently unavailable