fix: Refactor Bitbucket Cloud's OAuth2 host provider to support rotating refresh tokens - #2429
Draft
danielrfraser wants to merge 1 commit into
Conversation
…ting refresh tokens by always storing refresh tokens and access tokens against the configured git username
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
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.
Updates the
BitbucketHostProviderto retrieve (and store) refresh credentials using therequest.UserNamein all cases.Why?
Bitbucket Cloud is moving to rotating refresh tokens. These refresh tokens expire ~10 minutes after their first usage. The existing code (when running through the refresh token flow) would store the
refresh_tokenagainst the theremoteUri.GetUserName()however - theremoteUriwas built keeping theusernameintact.The initial authorize flow however
Fixes: #2428