API Access Management
Last Modified: 2026-11-12

API Access Management

You can securely manage API access from the Cloud Administration Console, under Platform>API Access Management.

RSA Resources

Manage access to the Cloud Administration and Authentication APIs. RSA supports both OAuth and legacy API key access methods for these APIs. For more information, see the following help pages:

Third-Party Resources

Register external resources and manage the clients that access them using tokens issued by RSA. You can define the scopes that govern each resource and choose what each client is allowed to do.

Register a Resource

Register an external API as a resource so that RSA issue tokens for it. Registration identifies the API and defines the scopes that determine what clients are allowed to do with it. Each resource must be registered before any API client can be granted access to it.

Procedure 

  1. In the Cloud Administration Console, click Platform>API Access Management.

  2. Click the 3rd-party resources tab.

  3. In the Resources section, click Register resource.

  4. On the Basic Information tab, complete these fields.

    1. In the Name field, enter a name for the resource. This field is required.

    2. (Optional) In the Description field, enter a description for the resource.

    3. In the Icon field, click Choose Icon and select the image you want to use. You can upload PNG, JPG, JPEG, or SVG files.

      Note:   Images larger than 512 x 512 pixels are resized automatically.

  5. Click Next Step.

  6. On the Resource Server Settings tab, complete these fields.

    1. In the Resource Identifier/Audience field, enter the unique identifier of the resource.

    2. In the Scope section, enter the Scope Name, Display Name, and Description, and then select a Consent. To add another scope, click Add.

    3. (Optional) Select Override default signing key checkbox. If you select this option, select the Signature Algorithm, and then in the JSON Web Key (JWK) field, paste your private JWK, or click Generate JWK.

    4. In the Max Access Token lifetime field, enter how long an access token for this resource remains valid, and then select the unit of time.

    5. In the Max Refresh Token Lifetime field, enter how long a refresh token remains valid, and then select the unit of time.

    6. In the Issuer URL field, click Copy URL to copy the issuer URL.

  7. Click Save.

  8. (Optional) To publish this configuration, click Publish Changes.

Add an API Client

This section provides instructions for adding an API client to the Cloud Administration Console. Adding an API client allows you to configure and manage access for clients that use the third-party resources you registered, providing detailed control over the permissions and security of each client.

Procedure 

  1. In the Cloud Administration Console, click Platform>API Access Management.

  2. Click the 3rd-party resources tab.

  3. In the OAuth Clients section, click Add API Client.

  4. On the Basic Information tab, complete these fields.

    1. In the Name field, enter a name for the OAuth client application. This field is required.

    2. (Optional) In the Description field, enter a description.

    3. In the Icon field, click Choose Icon and select the image you want to use. You can upload PNG, JPG, JPEG, or SVG files.

      Note:   Images larger than 512 x 512 pixels are resized automatically.

  5. Click Next Step.

  6. On the Authentication tab, complete these fields.

    1. The Authorization URL and Token URL fields are read-only and display the endpoints of the authorization server that issues the tokens.

    2. In the Redirect URL field, enter the URL where the client is redirected after client authentication. You can add multiple redirect URLs. To add another URL, click Add Redirect URL. The combined length of all redirect URLs cannot exceed 4,000 characters.

      Note:  The Redirect URL field is available only when Authorization Code is selected in the Grant Types section.

    3. The Client ID field is read-only and displays the unique identifier generated for this client. Record this value, because you need it later when you configure the client application.

    4. The Client Authentication field is read-only and is set to Private Key JWT.

    5. In the Client Secret field, enter the public key corresponding to the private key used by the client to sign the JWT. Alternatively, click Generate Secret to create a new secret. In the Key Pair Generator dialog box, specify the key type, click Generate Key Pair and then click Autofill.

      Note:  Download or copy the private key to a secure location before you close the dialog box. The client uses this key to sign the JWT.

    6. In the Grant Types section, select the grant types that the client can use.

      If you select Authorization Code (with PKCE), select an access policy from the 2.0 Access Policy for additional authentication drop-down list. This field is required.

    7. In the Network Zone drop-down list, select a network zone. Network zones are used to classify IP addresses as Trusted or Restricted, allowing you to manage and identify traffic coming into the application. For information about network zones, see Manage Networks.

    8. (Optional) Enable Allow CORS Authentication and enter the CORS URL.

  7. On the Resource and Scope tab, select the permissions that you want to grant to this client.

  8. Click Save and Finish.

  9. (Optional) To publish this configuration, click Publish Changes.

Dynamically Registered Clients

Dynamically registered clients are API clients, such as AI agents and Model Context Protocol (MCP) clients, that register themselves automatically without manual setup. Use this section to review and manage these clients. You can sort clients by Registered Date, use the AI Agent filter to show only AI agents, and expand a row to view the client's authentication method, grant types, and expiration date. You can also search for a client by client ID or name, and then edit or delete it.

Dynamic client registration is disabled by default. To enable and configure it, see Configure Dynamic Client Registration.

Edit a Registered Client

You can edit a dynamically registered client to update its name, description, icon, or network zone. The other Authentication fields and the client's credentials are read-only. Resource and scope configuration applies only to manually added clients.

Procedure 

  1. In the Cloud Administration Console, click Platform > API Access Management.

  2. Click the 3rd-party resources tab.

  3. Expand the Dynamically Registered Clients section, and click Edit next to the client you want to edit.

  4. On the Edit Client page, update the Name, Description, or Icon on the Basic Information tab, and the Network Zone on the Authentication tab.

  5. Click Save and Finish.

  6. (Optional) To publish this configuration, click Publish Changes.

Delete a Registered Client

You can delete a dynamically registered client you no longer need. Deleting a client ends its access.

Procedure 

  1. In the Cloud Administration Console, click Platform > API Access Management.

  2. Click the 3rd-party resources tab.

  3. Expand the Dynamically Registered Clients section, click the drop-down arrow next to the client you want to delete, and then select Delete.

  4. In the confirmation dialog box, click Delete.

  5. (Optional) To publish this configuration, click Publish Changes.