Handle issues when token is refreshed
See original GitHub issueIssue and Steps to Reproduce
After login, if a refresh token fail, for any reason, authenticating
component (declared into Provider
props) is indefinitely active while console expose the error below.
Is there a way, ideally at Provider level, to throw an Error component?
(I have already try with the sessionLostComponent
props of Provider
component, unsuccessfully)
Versions
“@axa-fr/react-oidc-context”: “^3.1.6”
Screenshots
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:11 (8 by maintainers)
Top Results From Across the Web
What Are Refresh Tokens and How to Use Them Securely
A refresh token can help you balance security with usability. Since refresh tokens are typically longer-lived, you can use them to request new ......
Read more >What Are Refresh Tokens and How Can They Boost Your ...
This guide will give an in-depth explanation of refresh tokens and discuss some best practices for creating and handling them.
Read more >Refresh Tokens - OAuth 2.0 Simplified
If you do not get back a new refresh token, then it means your existing refresh token will continue to work when the...
Read more >An in-depth look at refresh tokens in the browser
When the security token service detects that a refresh token is used more than once, it assumes that something is wrong. As a...
Read more >How to handle refresh tokens
The refresh token provides authorization to obtain a new access token, but does not authenticate that the person requesting the access token is ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry for the delay.
Thank you for taking the time to look and fix this bug.
I built the package from the
fix/refreshToken
branch and used the bundle in my client project: bug seems to be fixed.Hope it will be released soon.
I close the pullrequest. The v4 ans v5 version was rewritten is order to fix that kind of issue. The library is simpler ligther ans without that issue.
Thank you very much for your help. Feel free to reopen it if you need!