Repository navigation
feat(clients): support oidc_support on clients and client profiles - #1537
Open
harshithRai wants to merge 2 commits into
Open
harshithRai wants to merge 2 commits into
harshithRai wants to merge 2 commits into
Conversation
Add the oidc_support property to clients (including CIMD clients) and client_configuration.oidc_support to client profiles, in both YAML and directory formats. When the tenant does not have the feature enabled, the field is skipped with a warning and the rest of the configuration is applied. Co-Authored-By: Claude <noreply@anthropic.com>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1537 +/- ##
=======================================
Coverage 82.64% 82.65%
=======================================
Files 193 193
Lines 9301 9323 +22
Branches 2061 2066 +5
=======================================
+ Hits 7687 7706 +19
Misses 816 816
- Partials 798 801 +3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Cover the 403 status, errorCode and message conditions of the retry helper with dedicated tests, reuse the shared not-enabled error fixture, and document the dry-run, export and null behavior of oidc_support. Co-Authored-By: Claude <noreply@anthropic.com>
harshithRai
marked this pull request as ready for review
November 16, 2026 17:58
This file contains hidden or 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
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.
🔧 Changes
Adds support for the
oidc_supportproperty, which controls whether a client may use OIDC flows and which optional profile scopes (profile,email,address,phone) it may request. It applies to clients, including CIMD clients, and to client profiles throughclient_configuration.oidc_support, in both the YAML and directory formats.is_allowedis required, andallowed_scopesandallow_all_scopesare the scope options. Clients and client profiles share one schema definition.default_value, like the otherclient_configurationsettings.oidc_supportblock.oidc_supportfor that resource, logs a warning naming it, and applies the rest of the configuration, so a config exported from one tenant can still be deployed to another.Shape
The field is new on both resources. YAML, before:
YAML, after:
Directory (JSON), before,
clients/My Third-Party Application.json:{ "name": "My Third-Party Application", "oidc_conformant": true }Directory (JSON), after:
{ "name": "My Third-Party Application", "oidc_conformant": true, "oidc_support": { "is_allowed": true, "allowed_scopes": ["profile", "email"] } }Directory (JSON), after,
client-profiles/CIMD Client Profile.json:{ "name": "CIMD Client Profile", "client_configuration": { "oidc_support": { "default_value": { "is_allowed": true, "allow_all_scopes": true } } } }📚 References
N/A
🔬 Testing
Unit tests
Added in
test/tools/auth0/handlers/clients.tests.js:is_allowedwithallow_all_scopes, withallowed_scopes, and on its own asfalseopenidas a scope, a missingis_allowed, andnulloidc_supporton client create and updateoidc_supportwhen updating a CIMD clientoidc_supportand warns when the tenant does not have the featureAdded in
test/tools/auth0/handlers/clientProfiles.tests.js:default_valueclient_configuration.oidc_supporton profile create and updateAdded in
test/tools/utils.test.ts, for the shared retry helper:oidc_supportoidc_support, when the error is about something else, and when the status is not 403Updated
test/utils.jswith shared helpers for the not-enabled error and for capturing warnings.Manual verification
Against a live tenant, in both YAML and directory formats:
oidc_supporton a regular client, a strict third-party client, a CIMD client, and a client profile. Read each resource back through the Management API and confirm the stored value matches.allowed_scopestoallow_all_scopes) and import again. Confirm the stored value is replaced, not merged.--dry-runafter a successful import and confirm it reports no changes.allow_all_scopesandallowed_scopesand confirm the API's 400 is reported against the client.oidc_support, one warning is logged per resource, and the import succeeds.📝 Checklist