Implemented PKCE Authorization Flow #65
Closed
Conversation
This file contains 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
grdsdev
requested changes
Jul 31, 2023
grdsdev
requested changes
Aug 1, 2023
grdsdev
requested changes
Aug 4, 2023
grdsdev
requested changes
Aug 8, 2023
grdsdev
approved these changes
Aug 8, 2023
|
Closing in favor of: supabase/supabase-swift#119 |
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.
What kind of change does this PR introduce?
This PR consist implementation of PKCE Authorization Flow for
getOAuthSignInURL&signInWithOTPmethods.What is the current behavior?
What is the new behavior?
When initializing a client there is a new property called
flowTypewhich is of type FlowType enum that consist of two types:example:
let client = GoTrueClient(url: "", headers: [:], flowType: .pkce)The flowType property has default value of
.implicitAdditional context