[BAU] - Add error handling for session and token expiry #137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ceptions thrown by expired tokens and sessions
…ng the Nimbus OAuthError classes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
What changed
Why did it change
In order to align with RFC 6749 - The OAuth 2.0 Authorization Framework , we need to ensure when authorization codes are created, they have an expiry time set.
As per the RFC (above), this expiry time should have a maximum recommended TTL of 10 minutes.
Authorization codes must only be used once.
Once successfully changed for a bearer token, the authorization code must be expired.
Issue tracking