fix(auth): Revoke tokens intead of trying to end session #17
Conversation
This file contains hidden or 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
🦋 Changeset detectedLatest commit: c3a8058 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 changes the signout behavior. Instead of trying to end the session with a call to
/connect/endsession, we now call/connect/revocationto invalidate the refresh token.⛳️ Current behavior
On signout, an attempt to invalidate the session is made by calling
/connect/endsession.🚀 New behavior
On signout, the last received refresh token is invalidated with a call to
/connect/revocation💣 Is this a breaking change (Yes/No):
No
📝 Additional Information
This flow works better for device-flow implementations, but when authorization code flow is implemented we'll have to reintroduce the endsession endpoint.