[codex] fix login region endpoints#22
Merged
Merged
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
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.
Summary
Fix OAuth login so the service endpoints are built from the final region selected during login, instead of the region loaded from the old config before prompting.
Root cause
LoginAuthResolverconstructedauth.ServicebeforeAuthApp.Loginresolved and persisted the selected region. When a user switched fromtickticktodida365, login still used the previous TickTick OAuth endpoints for that run.Changes
AuthApp.cmd/ticklogin wiring to build the login auth service after the selected region is known.ticktickconfig todida365.Validation
go test ./...go build ./...go vet ./...