feat: add oauth config setting to enable/disable pkce extension #100
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
|
Hello, can you please consider reviewing and merging this PR. I think it is an important security feature that should be part of this library. Thank you. Best, Steffen |
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.
Describe the PR
Add Proof Key for Code Exchange Support configurable with the OAuthConfig struct.
Relation issue
#99
Additional context
OAuth2 clients that only support Authorization Code Flow with PKCE do not work with the current feature set of echo-swagger.
There is a flag for it in Swagger UI 3.24.0+: usePkceWithAuthorizationCodeGrant and these small changes fix the problem.