Implementation of the Authorization Code with PKCE flow for public clients #65
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
|
Any plans to merge it? authorization code grant type is now considered recommended one for public clients (i.e. SPA, mobile clients) and meat to replace implicit flow. So this PR gonna add quite some value. |
(cherry picked from commit bc4407b)
obukhov
reviewed
Dec 22, 2020
Co-authored-by: Alex Obukhov <a.a.obukhov@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is a (hopefully) complete implementation of the Authorization Code with PKCE flow (https://oauth.net/2/pkce/).