Skip to main content
Version: Latest (4.1.0)

Dynamic Client Registration (DCR) Policy

Dynamic Client Registration (DCR) lets OAuth clients register themselves with cidaas (RFC 7591) instead of an administrator creating every application in Trustdesk. The tenant DCR policy (policyType=dcr) is the single place that controls:

  • Whether open (unauthenticated) registration is allowed
  • Which client settings registered apps may use (ceilings)
  • Which values fill fields the registration document cannot carry (defaults)
  • How long client secrets live for confidential registrations (secrets)
  • How many DCR-created apps the tenant may hold (limits)

When DCR is enabled for the tenant, registration with an Initial Access Token (IAT) is always available. Open registration remains optional and is off by default.

Use case: Onboard partner tools or MCP hosts that must create OAuth clients under shared tenant rules, without creating each application manually and without handing out full app-management credentials.

When a registration request arrives, cidaas evaluates:

  1. Is DCR enabled for the tenant?
  2. Is the caller allowed to register — a valid IAT, or open registration enabled with no Bearer token?
  3. Do the requested client settings fit the ceilings?
  4. Which defaults, secrets, and limits apply?

If every check passes, cidaas creates the application and returns the registered client metadata (including a registration access token for later management under RFC 7592).

Availability

DCR must be enabled for your tenant. Contact cidaas support if it is not available yet. When DCR is disabled, DCR policy APIs return 404 (APP10161), and registration endpoints are not available.


Prerequisites​

Before configuring the DCR policy, ensure you have:

  1. DCR enabled for your tenant.
  2. An administrator account with the ADMIN or SECONDARY_ADMIN role, and the cidaas:apps_read (view) and cidaas:apps_write (save) scopes.
  3. Access to Trustdesk for your tenant (or the App Management Policies API).
  4. Agreement on which scopes, grant types, response types, auth methods, redirect URI rules, and token lifetimes registered clients may use.
  5. A decision on open registration (usually leave it off and use Initial Access Tokens for controlled onboarding).

Configuration Steps​

Step 1: Open the DCR policy​

  1. Sign in to Trustdesk as an administrator.
  2. Navigate to Integrations → App Management Policies.
  3. Open the DCR policy. When DCR is enabled, cidaas can create a default policy for your tenant (name is always default). There is nothing to create by hand.

The DCR policy cannot be deleted. To stop DCR, turn the feature off for the tenant or tighten ceilings / disable open registration as needed.

The seeded policy starts with these values:

SettingSeeded default
Open registrationOff
IAT registrationOn whenever DCR is enabled (not a separate policy toggle)
Allowed scopes / grant types / response types / auth methodsEmpty (nothing allowed until you fill them)
Max redirect URIs10 (platform max you may set: 50)
Redirect URI allow rulesEmpty (https plus loopback rules apply)
Max token / refresh token lifetime15 minutes / 30 days
Token / refresh token / authorization code lifetime (defaults)15 minutes / 30 days / 2 minutes
Secret expires in0 (never)
Max clients per tenant0 (unlimited)
Public client refresh tokensUnset (treated as none — public clients do not keep refresh_token)

Step 2: Choose how callers may register​

Open registration​

Open registration allows a caller to register without an Authorization header (anonymous DCR).

SettingTypical seeded defaultMeaning
Open registration enabledOffAnonymous registration is refused

Leave open registration off unless you intentionally allow anyone who can reach the registration endpoint to create clients. Prefer IATs for controlled onboarding.

Open registration is rate-limited per client IP (default tiers: 10 / 5 seconds, 30 / 1 minute, 100 / 5 minutes). Exceeding the limit returns 429 (APP10201). Requests that send a Bearer token are not counted against this limiter.

Security

Enabling open registration exposes client creation to unauthenticated callers (subject to your ceilings and rate limits). Use it only when that risk is accepted.

Initial Access Token registration​

When DCR is enabled, callers may register with Authorization: Bearer <initial-access-token>. Mint and manage IATs via /apps-srv/dcr/initial-access-tokens (scopes cidaas:dcr_iat_write / cidaas:dcr_iat_read).

The DCR policy does not turn IAT registration on or off separately — it follows the tenant DCR feature. Basic credentials are not accepted for registration.

Step 3: Configure ceilings​

Ceilings limit what a dynamically registered client may request. Empty allow-lists mean nothing in that category is allowed until you add values (not “allow all”). Until scopes, grants, response types, and auth methods are filled, most real registrations will fail or register with empty capabilities.

How a value outside the ceilings is treated:

Setting outside the ceilingResult
Grant type, response type, or auth methodThe registration is refused (invalid_client_metadata)
Redirect URI, or more redirect URIs than Max redirect URIsThe registration is refused (invalid_redirect_uri)
ScopeThe scope is removed; registration continues with the remaining scopes
refresh_token on a public client (auth method none)The grant is removed, unless Public client refresh tokens allows it
SettingTypical seeded defaultMeaning
Allowed scopesEmptyExact scope names only (no wildcards). Omitting scope in the document applies the full allow-list as the server default
Allowed grant typesEmptyGrant types the client may use
Allowed response typesEmptyResponse types the client may use
Allowed auth methodsEmptyToken endpoint auth methods (for example none, client_secret_basic, client_secret_post, client_secret_jwt, private_key_jwt, tls_client_auth, self_signed_tls_client_auth)
Max redirect URIs10Cap on redirect URI count (0 applies the platform default of 10; maximum configurable value is 50)
Redirect URI allow rulesEmptyOptional glob patterns over scheme://host:port/path; empty allows https (and loopback rules)
Max token lifetime15 minutes (900 s)Cap on access token lifetime (0 = tenant default as both default and cap)
Max refresh token lifetime30 daysCap on refresh token lifetime (0 = tenant default as both default and cap)
Public client refresh tokensUnset → nonenone drops refresh_token for public clients; dpopOnly keeps it only when DPoP-bound access tokens apply; allowed keeps it

Configure allow-lists to match the clients you intend to admit (for example openid, email, profile, authorization_code, refresh_token, code, and none or private_key_jwt).

Step 4: Configure defaults​

Defaults fill settings a registration document cannot carry. Lifetime defaults must not exceed the matching ceiling.

SettingTypical seeded defaultMeaning
Token lifetime15 minutesApplied when the document does not set it
Refresh token lifetime30 daysApplied when the document does not set it
Authorization code lifetime2 minutesApplied for interactive flows
Hosted pages layout IDEmptyTenant default layout when empty
User setup IDEmptyTenant default user setup when empty
Verification options / template group / group verification / group selection IDsEmptyTenant defaults when empty; applied to interactive clients
DPoP-bound access tokensOffApplied only when the document omits dpop_bound_access_tokens; a present member wins in either direction

Step 5: Configure secrets​

For confidential clients that receive a client secret at registration:

SettingTypical seeded defaultMeaning
Secret expires in0 (never)0 = no expiry; otherwise seconds until expiry (maximum 1 year / 31536000)

Step 6: Configure limits​

SettingTypical seeded defaultMeaning
Max clients per tenant0 (unlimited)Cap on total DCR-registered applications in the tenant

When the cap is reached, further registrations are refused until apps are removed or the limit is raised.

Step 7: Save​

  1. Review open registration, ceilings, defaults, secrets, and limits.
  2. Click Save.

A saved policy applies to the next registration. Existing registered apps keep the settings they were created with unless you update those apps separately (Trustdesk or RFC 7592 client management).


How registration uses the policy​

Register a client (RFC 7591)​

POST /apps-srv/dcr/clients

ModeAuthorizationWhen allowed
IATAuthorization: Bearer <iat>DCR feature enabled and IAT still valid
OpenNo Authorization headerOpen registration enabled on the policy

Typical flow:

  1. Caller sends client metadata (redirect URIs, grant types, and so on).
  2. cidaas authorizes the mode, applies ceilings / defaults / secrets / limits, and creates the app.
  3. The 201 response includes the registered client fields and a registration_access_token for later management.

Do not send HTTP Basic credentials on registration — they are refused.

Manage a registered client (RFC 7592)​

After registration, the client may manage itself with the registration access token:

ActionMethodPath
ReadGET/apps-srv/dcr/clients/{client_id}
ReplacePUT/apps-srv/dcr/clients/{client_id}
DeleteDELETE/apps-srv/dcr/clients/{client_id}

These calls authenticate with the registration access token (not an IAT). Full request and response details belong with the DCR registration API documentation;


Managing the policy via API​

The DCR policy uses the same App Management Policies routes as CIMD, with policyType=dcr (or type=dcr on list):

ActionMethodPath
List / seed defaultGET/apps-srv/app-management-policies?type=dcr
Get by idGET/apps-srv/app-management-policies/{id}
Create or replacePUT/apps-srv/app-management-policies
PatchPATCH/apps-srv/app-management-policies/{id}

Requires cidaas:apps_read / cidaas:apps_write and role ADMIN or SECONDARY_ADMIN.

Notable behaviour:

  • List with DCR disabled returns an empty list (200).
  • Get / save with DCR disabled returns 404 (APP10161).
  • PUT upserts: creates (201) if missing, replaces (200) if present.
  • Policy name must be default (400 APP10163 otherwise).
  • DELETE is always refused for DCR (400 APP10162).
  • Developer-portal style fields (groupIds, top-level allowedScopes) are not allowed on a DCR policy.
  • Other validation failures return 400 (APP10164) — for example defaults above ceilings, negative limits, or secrets.expiresInSeconds outside 0–31536000.

Verification​

  1. Open the DCR policy in Trustdesk and confirm open registration, ceilings, defaults, secrets, and limits match what you saved.
  2. Confirm allow-lists are filled for the clients you intend to admit.
  3. With open registration off, confirm an unauthenticated register call is refused (APP10197 / access denied).
  4. Mint an IAT via /apps-srv/dcr/initial-access-tokens, register a client with that Bearer token, and confirm success when metadata fits the ceilings.
  5. Confirm registration fails when a requested grant, auth method, or redirect URI is outside the ceilings, or when max clients per tenant is exceeded.
  6. Confirm scopes outside the allow-list are dropped rather than refusing the whole registration (unless no usable scopes remain for your use case).

Troubleshooting​

SymptomRoot causeRemediation
DCR policy missing / APIs return 404 APP10161DCR is not enabled for the tenantContact cidaas support to enable DCR
List returns empty with type=dcrDCR feature offEnable DCR; list seeds the default when the feature is on
Save returns 400 APP10163name is not defaultUse name: default
Save returns 400 APP10164Invalid ceilings, defaults, secrets, or limitsFix values (for example defaults above ceilings, negative limits, secret expiry out of range, unknown auth method)
Delete returns 400 APP10162DCR policy is not deletableDisable the feature or adjust policy settings instead
Unauthenticated register refused (APP10197)Open registration is offSend an IAT, or enable open registration only if intended
Register with Basic auth refused (APP10191)Basic credentials are not accepted for DCRUse an IAT Bearer token, or open registration with no Authorization header
IAT register refused (APP10193 / APP10194 / APP10195)IAT missing, expired, or exhaustedMint a new IAT or use a still-valid token
Open register rate-limited (APP10201)Too many anonymous registrations from the same IPRetry later or use IAT registration
Registration refused for metadataOutside ceilings (grants, response types, redirects, auth method, lifetimes)Widen ceilings or change the registration document
Tokens / scopes unexpected after registerScopes outside the allow-list were removedAdd the scopes to Allowed scopes
Public client has no refresh tokenPublic client refresh tokens mode is none (or unset)Set dpopOnly or allowed, or use a confidential auth method
Register refused for quotamaxClientsPerTenant reachedRemove unused DCR apps or raise the limit
Tokens / setup IDs unexpectedDefaults or empty IDs falling back to tenant defaultsSet explicit defaults on the DCR policy
RFC 7592 management unauthorized (APP10200)Registration access token missing or invalidUse the registration_access_token from the original register response

info
Need Support?

Contact cidaas support or [email protected].