user_token_replayed
| HTTP status | 401 |
| Area | Keys and SDK sessions |
Problem type |
https://docs.nexafone.so/errors/user_token_replayed |
Each user token works once (its jti is remembered). Have getUserToken fetch a fresh token from your server every time.
What the detail says
Section titled “What the detail says”The detail explains the occurrence; it can read, for example:
- This user token was already used. Sign a new one for every sign-in.
Handling it
Section titled “Handling it”Check the credential: send a valid, unrevoked key or a fresh token.
Example
Section titled “Example”{ "type": "https://docs.nexafone.so/errors/user_token_replayed", "title": "Unauthorized", "status": 401, "code": "user_token_replayed", "detail": "This user token was already used. Sign a new one for every sign-in.", "requestId": "01J9Z8Q4TQ3W6M5V2X7Y8Z9A0B"}Match on code, never on detail: the wording may change. See Problem Details.