Connecting Your Identity Provider
Connecting an identity provider (IdP) lets your organization's administrators sign in with their existing corporate credentials instead of the break-glass account, using standard single sign-on (OIDC), and maps IdP groups to Agent ID administrator access. You choose which groups in your identity provider are allowed to administer the console.
RSA Agent ID supports the following identity providers, shown as tiles on the Organization > Administrators page:
| Identity Provider | Supported Protocol(s) |
|---|---|
| Microsoft Entra ID | OIDC |
| Okta | OIDC |
| Keycloak | OIDC |
| PingOne | OIDC |
Administrator access is group-based rather than account-based: anyone in the identity provider groups you map here signs in as an administrator because access is granted from the group claim in their token, so there are no separate administrator accounts to create or invite.
The redirect URL Agent ID generates for administration console sign-in has the following format:
https://<admin-console-host>/admin/v1/login/callback/<agentid-tenant-id>
where <agentid-tenant-id> must be your exact Agent ID tenant ID, not your identity provider's own directory, environment, or
realm ID.
Procedure
- On Agent ID, click Organization in the left pane.
- Under Administration, click Administrators.
- Select the tile for your identity provider.
- In your identity provider's own administration console, register Agent ID as an application (web/OIDC type), using the Redirect URL Agent ID generates for the connection, and add a groups claim to the ID token so administrator group membership is included at sign-in.
- In Agent ID, type the resulting Issuer/discovery URL (for example, the provider's
.well-known/openid-configurationaddress), Client ID, and Client secret. - Under Admin groups, type or select the identity-provider group (by name or object/group ID) that should have administrator access, then click Add.
- Click Test and connect and confirm the displayed Redirect URL matches the one registered in your identity provider.
Results
Members of the mapped groups can now sign in with Continue with <your provider> instead of the break-glass administrator link.
After you finish
Review the administrator roster and, once an SSO administrator has signed in successfully, disable the break-glass account as described in Managing Administrators.
Note: The Client secret is stored encrypted after you save it and is never shown again in full. Rotate it from your identity provider's administration console if it is compromised. Client secrets expire after a maximum of 24 months in most providers—rotate before expiry rather than after sign-in starts failing.
For Microsoft Entra ID specifically, the application you register needs no API permissions beyond standard sign-in (openid, profile, email). Create it under Entra ID > App registrations > New registration with a Single tenant account type, add the groups claim under Token configuration > Add groups claim, and create a dedicated security group (for example Agent ID Admins) with Assigned membership to map under Admin groups.
Okta, Keycloak, and PingOne are supported through OIDC. Setup uses a standard OIDC application registration: a web application with a groups claim in the ID token (or an equivalent attribute mapping) and the Redirect URL that Agent ID generates. Configure it in the provider's own administration console before you complete the preceding procedure.
Related Articles
Connecting an Identity Provider to a Gateway 1Number of Views Connecting Discovery Data Sources 1Number of Views Connecting Microsoft Entra ID 1Number of Views Connecting AWS (IAM and Bedrock AgentCore) 1Number of Views Update an existing RSA Cloud Authentication Service Integrated Windows Authentication (IWA) Connector Identity Provider SA… 422Number of Views