Repository navigation
docs(oauth): explain redirect URIs for native apps - #161
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
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.
Adds a Native apps section to the OAuth guide. A custom scheme never passes the origin fallback and has to be listed in
redirectUris, and Google still refuses it on a web application client, so a Google button in a native app needs an https page that handscodeandstateto the app.The
detailvalue it names ships in fells-code/seamless-auth-api, in the PR titled "fix(oauth): record and log why an OAuth start failed". Merge after that one is released.Found through an Android app whose Google button failed on every tap.