feat: add support for allow_all_scopes property in clientGrants
#1278
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.
🔧 Changes
allow_all_scopesboolean property in Client Grants, which when enabled, allows all scopes configured on the resource server without explicitly listing themallow_all_scopesandscopeproperties - whenallow_all_scopesis true, thescopearray cannot be specifiedExamples
YAML format
JSON format (Directory structure)
{ "client_id": "My M2M Application", "audience": "https://api.example.com", "allow_all_scopes": true }📌 Note:
When
allow_all_scopesis set totrue, thescopeproperty must not be provided or must be empty🔬 Testing
allow_all_scopesandscopeare mutually exclusive and that valid configurations pass validationallow_all_scopesproperty📝 Checklist