Certified: May 11, 2026
Solution Summary
This guide describes integrating PingFederate with RSA Cloud Access Service (CAS) using SAML and OIDC. Use this information to determine which use case and integration type your deployment will employ.
Use Case
PingFederate can be integrated with RSA using SAML. When integrated, users must authenticate with RSA to sign in to PingFederate.
Integration Types
My Page SSO provides Single-Sign-On (SSO) to PingFederate 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.
Relying Party integration allows PingFederate users’ web browsers to be automatically redirected to CAS for authentication. With Relying Party integration, CAS can manage either additional authentication only or both primary authentication (for example, user ID and password) and additional authentication, depending on the service provider's capability.
Supported Features
This section shows all the supported features by integration type and by RSA components. Use this information to determine which integration type and RSA component your deployment will use. The next section in this guide contains the instruction steps for how to integrate RSA with PingFederate using each integration type.
PingFederate Integration with CAS
| Authentication Methods | RSA MFA API (REST) | RADIUS | Relying Party | My Page SSO |
| Approve | - | - | ||
| LDAP Password | - | - | ||
| SecurID OTP | - | - | ||
| Authenticate OTP | - | - | ||
| Device Biometrics | - | - | ||
| SMS OTP | - | - | ||
| Voice OTP | - | - | ||
| FIDO Security Key | - | - | ||
| QR Code | - | - | ||
| Emergency Access Code | - | - |
| Supported | |
| - | Not supported |
| n/t | Not yet tested or documented, but may be possible |
| n/a | Not applicable |
Configuration Summary
This section contains instruction steps that show how to integrate PingFederate 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 PingFederate 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.
Integration Configuration
CAS
SAML
- PingFederate - My Page SSO Configuration Using SAML- RSA Ready Implementation Guide
- PingFederate - Relying Party Configuration Using SAML - RSA Ready Implementation Guide
OIDC
- PingFederate - My Page SSO Configuration Using OIDC - RSA Ready Implementation Guide
- PingFederate - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide
RSA Terminology Changes
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 |
| Cloud Authentication Service | Cloud Access Service | |
| Token | OTP Credential | SecurID OTP Credential |
| Authenticator | Hardware Authenticator | |
| Tokencode | OTP | SecurID OTP, SMS OTP, Voice OTP |
| Access Code | Emergency Access Code | |
| SecurID Authenticate app | RSA Authenticator app | RSA Authenticator app for iOS and Android, RSA Authenticator app for Windows |
| Device | Authenticator | Register an authenticator |
| Company ID | Organization ID | |
| Account | Credential | |
| Device Serial Number | Binding ID |
Certification Details
CAS
Ping Identity PingFederate 12.2
Known Issues
No known issues
