Users getting logged out with "Unsuccessful Refresh Token exchange, reused refresh token detected"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- authentication, frontend
Research direction
Start with the auth0-react Sample-01 app and inspect the Auth0Provider configuration and getAccessTokenSilently usage described in the report. Trace refresh-token handling with cacheLocation="localstorage" and useRefreshTokens enabled, then reproduce the intermittent exchange failure if possible. Done means the cause of the reused-token logout is identified and the affected behavior is verified across the reported environments.
Written by the indexing model from the issue text.
Description
Checklist
- The issue can be reproduced in the auth0-react sample app (or N/A).
- I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
- I have looked into the API documentation and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
Description
Our usage of Auth0 is pretty simple. After the user has been logged in we just attach the access token to network calls and verify them server side.
const useApi = (): Api => {
const { getAccessTokenSilently } = useAuth0()
const backend = axios.create({ baseURL: apiUri, timeout: 10000 })
backend.interceptors.request.use(
async config => {
const accessToken = await getAccessTokenSilently()
config.headers["Authorization"] = `Bearer ${accessToken}`
return config
},
async error => {}
)
}
We have gotten user reports that they get error in title. Our understanding is that this error is unrecoverable so we log the user out and force them to re-authenticate. We have a couple of thousand weekly users and this happens to maybe 2% of them.
One log id as an example:
90020251109193144192993000000000000001223372093304300940
Our top level provider:
<Auth0Provider
key={`${domain}-${clientId}-${audience}`} // This forces remount when values change
domain={domain}
clientId={clientId}
authorizationParams={{
redirect_uri: getFrontEndHost(),
audience: audience,
}}
cacheLocation={"localstorage"}
onRedirectCallback={onAuth0Redirect}
useRefreshTokens={true}
>
<AppWithTheme />
</Auth0Provider>
Reproduction
Seems to happen randomly, a few times a week for affected users. Mostly on iOS and MacOS devices but we've also seen it happen on Windows machines.
Additional context
A similar issue happens when we use the react native version, but only for iOS devices. We allow overlap for expiring refresh tokens (120 seconds). Our refresh token are set to last one year, and we're currently seeing this multiple times a week for users.
auth0-react version
2.8.0
React version
19.1.0
Which browsers have you tested in?
Chrome, Safari
- Dominant language
- TypeScript
- Stars
- 992
- Forks
- 292
- Avg merge
- 10h 29m
- Merged PRs (30d)
- 24
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from auth0/auth0-react
-
auth0-spa-js enhancement
Difficulty 4/5 3-5 days Newbie friendliness 42/100
auth0/auth0-react#1321 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
auth0/auth0-react#562 · 14 comments ·
Maintainers usually reply within 1 day
All issues in auth0/auth0-react
Similar issues
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Openarea: @angular/build
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
angular/angular-cli#34764 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30384 · 1 comment ·
Maintainers usually reply within 1 day
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day