Certified: June 14, 2023
This section describes Federated Directory integration with RSA (or ID Plus). Use this information to determine which use case and integration type your deployment will employ.
Federated Directory can be integrated with RSA using SSO and Relying Party. When integrated, users must authenticate with RSA to sign in to Federated Directory.
SSO integrations use SAML 2.0 or HFED technologies to direct users’ web browsers to Cloud Authentication Service for authentication. SSO provides Single Sign-On using the IDR My Applications/My Page Portal. My Page SSO provides Single-Sign-On (SSO) to Federated Directory users leveraging RSA self-service portal, My Page. Both SP-initiated SSO and IdP-initiated SSO are supported. Modern Cloud-hosted SSO with My Page replaces the existing SAML SSO support with the IDR. Existing SSO integrations using IDR My Applications continue to be supported and are listed in this document as applicable.
Note: RSA will continue to maintain existing SAML SSO integrations using IDR My Applications. At a to-be-determined future date, RSA will announce the end-of-life (EOL) date for the SAML SSO support with the IDR. For more information, see Available Now: My Page SSO Enhancements - RSA Community - 680715.
Relying Party integration allows Federated Directory users’ web browsers to be automatically redirected to RSA Cloud Authentication Service for authentication. With Relying Party integration, Cloud Authentication Service can manage only additional authentication or both primary authentication (for example, user ID and password) and additional authentication.
This section shows all the supported features by integration type and by RSA components. Use this information to determine which integration type and which RSA component your deployment will use. The next section in this guide contains the instruction steps for how to integrate RSA with Federated Directory using each integration type.
Authentication Methods |
RSA MFA API (REST) |
RADIUS |
Relying Party |
SSO |
Approve |
- |
- |
||
LDAP Password |
- |
- |
||
SecurID OTP |
- |
- |
||
Authenticate OTP |
- |
- |
||
Device Biometrics |
- |
- |
||
SMS OTP |
- |
- |
||
Voice OTP |
- |
- |
||
FIDO Security Key |
- |
- |
Authentication Methods |
RSA MFA API (REST) |
RADIUS |
Authentication Agent |
---|---|---|---|
RSA SecurID | - | - | - |
On Demand Authentication | - | - | - |
Risk-Based Authentication | - | - | - |
|
Supported |
- |
Not supported |
n/t |
Not yet tested or documented, but may be possible |
n/a |
Not applicable |
This section contains instruction steps that show how to integrate Federated Directory with RSA using all of the integration types.
This document is not intended to suggest optimum installations or configurations. It is assumed that the reader has both working knowledge of all products involved, and the ability to perform the tasks outlined in this section. Administrators should have access to the product documentation for all products to install the required components.
All RSA and Federated Directory components must be installed and working prior to the integration.
This section of the guide includes links to the appropriate sections for configuring both sides for each use case.
The following table describes the differences in the terminologies used in the different versions of RSA products and components.
Previous Version |
New Version |
Examples/Comments |
---|---|---|
Company ID | Organization ID | |
Account | Credential | |
Token | OTP Credential |
SecurID OTP Credential |
Tokencode | OTP/Access Code |
SecurID OTP, SMS OTP, Voice OTP Emergency Access Code, Disable Access Code |
Hardware Token | Hardware Authenticator | |
Device Serial Number | Binding ID | |
Device | Credential/Authenticator | |
Device Registration Code | Registration Code | |
Authenticate App | Authenticator App |
No known issues.
RSA Cloud Authentication Service
Federated Directory