Authorization code grant without client_secret #7
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
Addresses issue antechrestos#5 which seems to be the only missing piece to get PKCE authentication working with Okta PKCE auth for a native application deployment.
timgates42
force-pushed
the
feature/pkce_authorization_header
branch
2 times, most recently
from
6293c0c
to
f81cabc
Compare
|
@timgates42 We met issue with the implementation of public oauth api with cloudfoundry client: this late one defaultly set client id to Deducing public api with I mae some change in #15 to make the distinction. That will be releeased in 1.4.2 |
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.
Addresses issue #5 which seems to be the only missing piece to get PKCE
authentication working with Okta PKCE auth for a native application
deployment.
Closes #5