Merging to release-5.7.0: [TT-13535/TT-13566] make upstream oauth password client secret not required (#6701) #6707
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.
User description
TT-13566
[TT-13535/TT-13566] make upstream oauth password client secret not required (#6701)
Description
make upstream oauth password client secret not required
Related Issue
Parent: https://tyktech.atlassian.net/browse/TT-13535
Subtask: https://tyktech.atlassian.net/browse/TT-13566
Motivation and Context
How This Has Been Tested
Screenshots (if appropriate)
Types of changes
functionality to change)
coverage to functionality)
Checklist
why it's required
explained why
PR Type
Enhancement
Description
clientSecret
in the OAuth password flow schema, making it optional.Changes walkthrough 📝
x-tyk-api-gateway.json
Make `clientSecret` optional in OAuth password schema
apidef/oas/schema/x-tyk-api-gateway.json
clientSecret
from the list of required fields.clientSecret
optional for OAuth passwordflows.