feat(oauth): add provider buttons + callback route to auth screens#44
Merged
Conversation
The sign-in view lists configured providers as 'Continue with <provider>' buttons that startOAuthLogin and redirect to the IdP; a new /oauth/callback route reads code/state and calls finishOAuthLogin, then lands on the app. Fixes #43.
This was referenced Jun 29, 2026
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.
Fixes #43.
What
Adds OAuth provider UI to the built-in auth screens, so apps using
AuthRoutesget a workingOAuth login without hand-rolling it. The SDK already had the client methods
(
listOAuthProviders,startOAuthLogin,finishOAuthLogin); this wires the UI and callback.Changes
OAuthProviderButtons: lists configured providers (listOAuthProviders) as"Continue with " buttons on the sign-in view. Selecting one calls
startOAuthLogin(with
redirectUri = <origin>/oauth/callback), stashes the provider id insessionStorage,and redirects to the IdP's
authorizationUrl.OAuthCallback+ the/oauth/callbackroute: readscode/statefrom the URL and thestashed provider id, calls
finishOAuthLogin, then lands the user on the app.Tests
listOAuthProviders(the view now renders the buttons).Pairs with fells-code/seamless-auth-api#50 (OAuth provider config defaults), which the OAuth flow
depends on. The
seamless verifyharness adds a browser OAuth case on top of this.