fix(backend): Replace session-token-outdated
error with more specific errors
#4205
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR replaces the
'session-token-outdated'
auth error reason with the following 4 more specific ones:'session-token-expired'
: Session token has expired.'session-token-iat-before-client-uat'
: Session token was issued before the timestamp depicted in__client_uat
'session-token-not-active-yet'
: Current time was before session token's nbf claim (possible clock skew)'session-token-iat-in-the-future'
: Session token was issued in the future (possible clock skew)Checklist
npm test
runs as expected.npm run build
runs as expected.Type of change