Invalidate cached OAuth tokens when profiles change - #6427
Draft
mihaimitrea-db wants to merge 1 commit into
Draft
Conversation
Collaborator
Integration test reportCommit: edc6045
Top 3 slowest tests (at least 2 minutes):
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changes
Store a fingerprint of the complete saved profile with cached OAuth credentials and validate it before token reuse or refresh. Legacy tokens without fingerprint metadata require one new login.
Why
Cached OAuth grants can become inconsistent with manually edited profile configuration. Failing closed prevents a token minted for one profile configuration from being reused with another.
Tests