Add oauth2 PKCE test case #21389
Open
Add oauth2 PKCE test case #21389
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
|
PR builder started |
5 tasks
|
PR builder completed |
jenkins-is-staging
approved these changes
Oct 17, 2024
There was a problem hiding this comment.
Approving the pull request based on the successful pr build https://github.com/wso2/product-is/actions/runs/11378848413
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.
Public Issue : #21313
Currently we don't have a test suite to test PKCE scenarios in integration test nodule, but we have one in scenario test which cover legit customer scenario which is not sufficient for testing edge cases and frequent changes in oauth repo. Hence this PR will address above isue.
Verified scenarios are,
Default App
Mandate PKCE for the App withot allowing Plain challenge method
Mandate PKCE for the App with allowing Plain challenge method