Configure Dynamic Client Registration
You can configure dynamic client registration to control how AI agents and Model Context Protocol (MCP) clients register with your OAuth authorization server. When you configure dynamic client registration, you can control which clients can register, limit how many can register, and set how long each client remains active.
Dynamic client registration is disabled by default. After you enable and configure it, you can manage registered clients in the Dynamically Registered Clients section under Platform > API Access Management. For more information, see API Access Management.
Procedure
In the Cloud Administration Console, click Platform > Dynamic Client Registration.
Under General Settings, enable Allow Dynamic Client Registration. This option allows inbound client registration requests.
In the Lifetime field, enter how long a dynamically registered client remains active, and then select the unit of time: seconds, minutes, hours, days, or months. The default is 14 days. Clients are deleted automatically when the lifetime ends.
Under Registration Gatekeeping & Anti-Abuse, do the following:
(Optional) To require an initial access token for registration requests, select Require Initial Access Token (IAT) for registration payloads. In the Access Token Lifetime field, enter the number of hours that the initial access token remains valid. Enter a value from 1 to 720. The default is 1 hour.
Click Generate Initial Access Token, and then copy the token and store it securely. You can view the token only once.
Select at least one of the following limits, and then enter its value:
Select Max Registrations per IP (Hourly), and then enter the maximum number of registrations that one IP address can submit each hour.
Select Max Registrations per Tenant (Hourly), and then enter the maximum number of registrations that your tenant accepts each hour.
Select Max Active Clients per Tenant, and then enter the maximum number of active dynamically registered clients.
From the Network Zone list, select a network zone.
Under Client Authentication Methods and Grant Types, do the following:
In the Allowed Authentication Methods field, select the methods that clients can use to authenticate at the token endpoint:
Client Secret Basic
Client Secret Post
Client Secret JWT
Private Key JWT
None: The client sends token requests without client authentication. User authentication and access policies still apply.
In the Allowed Grant Types field, select one or more grant types that clients can use. If you select the Authorization Code grant type, select an access policy from the Access Policy for additional authentication list.
Authorization Code
Client Credentials
Refresh Token
Under Approval Workflow Policy, the Approval Workflow is set to Fully Automated (JIT) by default.
Click Save.
Click Publish Changes.
Related Articles
Dynamic Seed provisioning using QR Code 814Number of Views How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle 2.42KNumber of Views RADIUS shared secret limitations of RADIUS clients configured with RSA Authentication Manager 762Number of Views Distribute One Software Token Using Dynamic Seed Provisioning 108Number of Views Unsuccessful Registration of the RSA Authenticator app for iOS or Android with a registration code from the Cloud Administ… 694Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) Replication Showing Internal Replication Error During Upgrade to RSA Authentication Manager 8.2