Connecting an Identity Provider to a Gateway
Last Modified: 2026-11-19

Connecting an Identity Provider to a Gateway

Administration console sign-in is separate from the identity provider a gateway uses to authenticate the people and agents calling through it—that connection is configured once per gateway, in addition to (not instead of) administration console SSO.

For Microsoft Entra ID, Okta, Keycloak and PingOne, Agent ID creates the sign-in broker application. For RSA ID Plus, you create the broker client yourself.

Microsoft Entra ID

Before you begin

For Microsoft Entra ID, gateway federation needs the following application registrations created up front:

  • An API application (for example, RSA Agent ID Secure API) that exposes a single custom scope (for example, AgentID.Access) under Expose an API. The API application's Application (client) ID becomes the gateway's Audience value. Follow the below instructions:

    1. Under Expose an API, set the Application ID URI (keep api://<client-id>) and add exactly one scope.
    2. In the manifest, set requestedAccessTokenVersion to 2.
    3. Under Token configuration, add a groups claim (Security groups, Group ID).
    4. Enter the client ID as the Audience value without api://.
  • A Registrar application (for example, RSA Agent ID Secure Registrar) granted the Microsoft Graph application permissions Application.ReadWrite.OwnedBy, User.Read.All, and Group.Read.All, with admin consent granted for all three. The Registrar application's Client ID and Client secret let Agent ID provision gateway/agent applications on your behalf.

Procedure

  1. On the Gateways page, click Configure under the Identity provider column for the intended gateway.

  2. Under Identity provider, select Microsoft Entra ID.

    To enter the endpoints manually instead of using the Discovery URL, turn on Manual configuration.

  3. Enter the Discovery URL of the identity provider; endpoints populate automatically.

  4. Enter the API application's client ID in Audience value, the Registrar application's client ID in Registrar client ID, its secret in Registrar client secret, and the directory/tenant ID in Azure AD tenant/directory ID.

  5. Click Test Connection, then click Save.

  6. Publish the gateway (For more information, see Publishing Configuration Changes).

Results

Agent ID creates the gateway's sign-in broker application in your directory, owned by the Registrar application. Agents and users calling through this gateway now authenticate against the connected identity provider, and the groups carried in their tokens determine which tools they can see. For more information, see Roles and Scopes.

Okta

Before you begin

Ensure you have the following:

  • Okta API Access Management. Your Okta organization must include custom authorization servers. To check, go to Security > API > Authorization Servers. You cannot use Okta's built-in org authorization server, because other services cannot validate the tokens it issues.

  • Super Administrator role. You must be signed in as a Super Administrator to create the authorization server, create the custom admin role, and assign admin roles.

  • Users who can meet your Okta sign-in policy. Okta evaluates each app's authentication policy before it lets a user sign in. Every new app, including each agent app that RSA Agent ID Secure creates, gets your organization's default policy. Make sure the people who will use agents can meet that policy's requirements, such as a second authentication factor. If they cannot, Okta denies the sign-in with the error "The resource owner or authorization server denied the request." You can assign a different policy to the admin console app on its Sign On tab.

  • A custom authorization server for the gateway. Create one in Security > API > Authorization Servers, with these settings:

    • Audience: a unique identifier for your gateways, for example https://agentid.<your-domain>. Enter this value as the Audience value in the procedure.

    • Access policy: a policy assigned to All clients, with a rule that allows the Authorization Code grant type, any user assigned the app, and any scopes. Keep the default token lifetimes.

    • Claim: a groups claim included in the Access Token, with value type Groups, filter Matches regex .*, and included in any scope. If you set up admin console single sign-on, add a second claim with the same settings for the ID Token.

    • Note the Issuer on the server's Settings tab. You need it for the Discovery URL.

  • A group for the people who will use agents. Create it in Directory > Groups, add those people, and note its group ID. This becomes the Assignment group ID.

  • A dedicated registrar administrator with an API token. RSA Agent ID Secure manages Okta apps through the Okta Management API, and an API token has exactly the permissions of the administrator who creates it. To limit those permissions:

    1. Create a custom admin role with these permissions: View application and its details, Edit application's authentication and integration details, Manage group's app assignment, and View users and their details.
    2. Create a resource set containing all applications, all groups, and all users.
    3. Create a dedicated user account used only for this purpose.
    4. Assign the user the custom role with that resource set. Temporarily also assign Read-only Administrator, because the custom role cannot create API tokens.
    5. Sign in as that user, create an API token in Security > API > Tokens, and copy it. Okta shows the token only once.
    6. Sign back in as yourself and remove Read-only Administrator from the user. The token keeps only the custom role's permissions.

Procedure

  1. On the Gateways page, click Configure under the Identity provider column for the intended gateway.

  2. Under Identity provider, select Okta.

  3. Enter the Discovery URL of your Okta authorization server. The Authorization endpoint, Token endpoint, and JWKS URI fields populate automatically.

    For a custom authorization server, the format is https://<your-okta-domain>/oauth2/<authorizationServerId>/.well-known/openid-configuration. For the built-in custom authorization server, the ID is default.

  4. Enter the following values:

    • Audience value: The audience of the authorization server. In Okta, the audience is set when the authorization server is created, and it is shown on the server's Settings tab.

    • Okta API token: An Okta API token. Okta shows the token value only once, when you create it, so copy it immediately. The token has the same privileges as the administrator who created it, and its privileges change if that administrator's privileges change. Agent ID uses the token regularly, so it doesn't expire from disuse; it stops working if its administrator is deactivated or loses the registrar role.

    • Assignment group ID: The ID of the Okta group. In Okta, go to Directory > Groups, open the group, and copy the ID from the end of the browser URL. Group IDs start with 00g.

      Without an assignment group, no one can sign in through the agent apps this gateway creates.

    • CIBA authenticator ID: The ID of the Custom Authenticator that Okta uses for CIBA (Client-Initiated Backchannel Authentication). In Okta, go to Security > Authenticators, open the Actions menu for the authenticator, click Authenticator ID & Info, and copy the ID. Authenticator IDs start with aut.

  5. Click Test Connection, then click Save.

  6. Publish the gateway (For more information, see Publishing Configuration Changes).

Keycloak

Before you begin

Create the following in your Keycloak realm before you connect the gateway:

  • A client scope for the gateway. In your Keycloak realm, go to Client scopes > Create client scope and configure it as follows:

    • Name: rsa-agentid-secure. Type: Default. Protocol: OpenID Connect. Turn off Display on consent screen and Include in token scope.

    • Add an Audience mapper. Set Included Custom Audience to a unique identifier for your gateways, for example https://agentid.<your-domain>. Enter this value as the Audience value in the procedure. Turn on Add to access token and turn off Add to ID token.

    • Add a Group Membership mapper. Set Name and Token Claim Name to groups. Turn off Full group path. Turn on Add to access token and turn off Add to ID token.

  • A registrar client. RSA Agent ID Secure uses this client to create the sign-in broker client in your realm. Go to Clients > Create client and configure it as follows:

    • Client type: OpenID Connect. Client ID: rsa-agentid-secure-registrar. Turn on Client authentication. For the authentication flow, select only Service accounts roles, and clear Standard flow and Direct access grants. This client ID is the Registrar client ID in the procedure.

    • On the Service accounts roles tab, assign the manage-clients and view-users roles from the realm-management client.

    • On the Credentials tab, copy the Client secret. This is the Registrar client secret in the procedure.

Procedure

  1. On the Gateways page, click Configure under the Identity provider column for the intended gateway.

  2. Under Identity provider, select Keycloak.

  3. Enter the Discovery URL of your Keycloak realm. The endpoints populate automatically.

    The format is https://<host>/realms/<realm-name>/.well-known/openid-configuration. If your Keycloak deployment uses a path in its hostname setting (for example, /auth), that path is part of the URL.

  4. Enter the following values:

    • Audience value: The Included Custom Audience of the rsa-agentid-secure client scope's Audience mapper. Enter it exactly as set in Keycloak.

    • Registrar client ID: The Client ID of the Keycloak client. In Keycloak, go to Clients and select the client.

    • Registrar client secret: The client secret. In Keycloak, the secret is on the Credentials tab of the client. The tab is available when Client authentication is turned on under Settings > Capability config.

  5. Click Test Connection, then click Save.

  6. Publish the gateway (For more information, see Publishing Configuration Changes).

PingOne

Procedure

  1. On the Gateways page, click Configure under the Identity provider column for the intended gateway.

  2. Under Identity provider, select PingOne.

  3. Enter the Discovery URL of your PingOne environment. The endpoints populate automatically.

    The format is https://auth.pingone.<domain>/<environmentId>/as/.well-known/openid-configuration. The domain depends on the region of your environment: com (North America), ca (Canada), eu (European Union), com.au (Australia), sg (Singapore), or asia (Asia-Pacific). In the PingOne admin console, the environment ID is under Settings > Environment Properties.

  4. Enter the following values:

    • Audience value

    • Registrar client ID

    • Registrar client secret

    • DaVinci flow policy ID

  5. Click Test Connection, then click Save.

  6. Publish the gateway (For more information, see Publishing Configuration Changes).

RSA ID Plus

Procedure

  1. On the Gateways page, click Configure under the Identity provider column for the intended gateway.

  2. Under Identity provider, select RSA ID Plus.

  3. Enter the Issuer URL of your RSA ID Plus tenant. The Authorization endpoint, Token endpoint, and JWKS URI fields populate automatically.

    To copy the issuer URL, in the ID Plus Administration Console, go to Platform > API Access Management. In the Issuer URL field, click Copy URL.

  4. Enter the following values:

    • Audience value

    • Admin API Client ID: The client ID of an Admin API client.

      • To create the client, in the ID Plus Administration Console, go to Platform > API Access Management. Under OAuth Clients, click Add API Client. The Client ID is generated and displayed read-only.

      • Give this client the User > rsa.user.read and Local Group > rsa.group.read permissions on the Resource and Scope tab, then click Publish Changes.

      • To assign roles by group, map the groups claim in OIDC Settings to localGroups. The default groups claim is a constant.

    • Admin API Private Key: The private key for the Admin API client. The client uses Private Key JWT authentication. In the Client Secret field, click Generate Secret, click Generate Key Pair, and then click Autofill. Download or copy the private key before you close the dialog box.

    • Initial Access Token: In the ID Plus Administration Console, go to Platform > Dynamic Client Registration. Select Require Initial Access Token (IAT) for registration payloads, then click Generate Initial Access Token. Copy the token and store it securely. The token is displayed only once.

    • Broker client ID: The ID of the OAuth client created for this gateway in the ID Plus Administration Console. Push approvals go through this client, so first select CIBA (Poll) on it in ID Plus.

    • Broker client secret

  5. Click Test Connection, then click Save.

  6. Publish the gateway (For more information, see Publishing Configuration Changes).