feat(op): PKCE Verification in Legacy Server when AuthMethod is not NONE and CodeVerifier is not Empty #496
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.
Related to Issue 254 and Issue 6886
Authorization Code + PKCE is the most secure and commonly recommended authentication method when referencing many Social Providers and IDP's.
This change is primarily to enable PKCE verification when using Code method - how this will be implemented will be determined internally by Zitadel team (e.g. an option in current method, or a new method a user can choose).
Definition of Ready