Skip to content

Conversation

@kushalshit27
Copy link
Contributor

@kushalshit27 kushalshit27 commented Jan 27, 2026

🔧 Changes

  • Added support for the allow_all_scopes boolean property in Client Grants, which when enabled, allows all scopes configured on the resource server without explicitly listing them
  • Add validation between allow_all_scopes and scope properties - when allow_all_scopes is true, the scope array cannot be specified

Examples

YAML format
clientGrants:
  - client_id: "My M2M Application"
    audience: "https://api.example.com"
    allow_all_scopes: true
JSON format (Directory structure)
{
  "client_id": "My M2M Application",
  "audience": "https://api.example.com",
  "allow_all_scopes": true
}

📌 Note:

When allow_all_scopes is set to true, the scope property must not be provided or must be empty

🔬 Testing

  • Added 2 validation tests to ensure allow_all_scopes and scope are mutually exclusive and that valid configurations pass validation
  • Added process test to verify client grants can be created with allow_all_scopes property

📝 Checklist

  • All new/changed/fixed functionality is covered by tests (or N/A)
  • I have added documentation for all new/changed functionality (or N/A)

- src/tools/auth0/handlers/clientGrants.ts: add allow_all_scopes property to schema and implement validation logic
- src/tools/auth0/handlers/prompts.ts: update ScreenRenderer type to Management.GetAculResponseContent
- test/tools/auth0/handlers/clientGrants.tests.js: ensure scope is not allowed when allow_all_scopes is true
- test/tools/auth0/handlers/clientGrants.tests.js: validate successful creation of client grants with allow_all_scopes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants