Update 10-OAuth-2-PKCE.md #63
Open
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
> Base64 URL Encoded (without padding) string containing the SHA-256 digested form of the clients one-time random 128 byte verifier (also in Base64URLEncoded form without padding). "clients" is incorrect, needs to be "client's" "128 byte verifier" is incorrect - it's 128-byte *after* the verifier is base64-encoded. Actual verifier can be somewhere between 90 and 110 bytes; example code uses 93, so let's go with that.
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.
"clients" is incorrect, needs to be "client's"
"128 byte verifier" is incorrect - it's 128-byte after the verifier is base64-encoded. Actual verifier can be somewhere between 90 and 110 bytes; example code uses 93, so let's go with that.
Description
Jira Ticket
Before Merging!