Certified: May 26th, 2020
Solution Summary
Use Case
When integrated, Britive end users must authenticate with RSA SecurID Access to sign in. Britive can integrate using SSO Agent or Relying Party.
Integration Types
SSO Agent integrations use SAML 2.0 to direct users’ web browsers to Cloud Authentication Service for authentication. SSO Agents also provide Single Sign-On to other applications using the RSA Application Portal.
Relying party integrations use SAML 2.0 to direct users’ web browsers to Cloud Authentication Service for authentication.
Supported Features
This section shows all of the supported features by integration type and by RSA SecurID Access component. Use this information to determine which integration type and which RSA SecurID Access component your deployment will use. The next section in this guide contains the steps to integrate RSA SecurID Access with Britive for each integration type.
Britive Integration with RSA Cloud Authentication Service
| Authentication Methods | Authentication API | RADIUS | Relying Party | SSO Agent SAML |
|---|---|---|---|---|
| RSA SecurID | - | - | ||
| LDAP Password | - | - | ||
| Authenticate Approve | - | - | ||
| Authenticate Tokencode | - | - | ||
| Device Biometrics | - | - | ||
| SMS Tokencode | - | - | ||
| Voice Tokencode | - | - | ||
| FIDO Token | n/a | n/a | ||
| Identity Assurance | - | - | - | - |
Britive Integration with RSA Authentication Manager
| Authentication Methods | Authentication API | RADIUS | Authentication Agent |
|---|---|---|---|
| RSA SecurID | - | - | - |
| On-Demand Authentication | - | - | - |
| Risk-Based Authentication | n/a | - | - |
| Supported | |
| - | Not supported |
| n/t | Not yet tested or documented, but may be possible. |
| n/a | Not applicable |
Configuration Summary
The following links provide instructions on how to integrate Britive with RSA SecurID Access.
This document is not intended to suggest optimum installations or configurations. It assumes 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 in order to install the required components. All RSA SecurID Access and Britive components must be installed and working prior to the integration.
Integration Configuration
Certification Details
Date of testing: May 20th, 2020
RSA Cloud Authentication Service
Britive Release.2020.05.02
Known Issues
No known issues.
Related Articles
Okta SSO - SAML Relying Party Configuration as a step-up for Okta applications - RSA Ready SecurID Access Implementation G… 88Number of Views RADIUSwith AM Configuration - Cisco FTD RSA Ready SecurID Access Implementation Guide 94Number of Views Microsoft Entra ID External MFA - RSA Ready Implementation Guide 649Number of Views Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide 701Number of Views Palo Alto NGFW - RSA Ready Implementation Guide 410Number of Views
Trending Articles
Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update Authentication Manager How to Retrieve the LDAPS Certificate and Configure an External Identity Source to Use LDAPS