Certified: October 14, 2026
Solution Summary
This guide describes Google Cloud Workforce Identity integration with RSA ID Plus using SAML 2.0. Use this information to determine which use case and integration type your deployment will employ.
Use Case
Google Cloud Workforce Identity can be integrated with RSA ID Plus using SAML Relying Party and SAML My Page. When integrated, users must authenticate with RSA to sign in to Google Cloud Workforce Identity.
Integration Types
SSO integrations use SAML 2.0 or HFED technologies to direct users' web browsers to Cloud Access Service (CAS) for authentication. The integration provides Single Sign-On (SSO) using Relying Party and My Page.
- Relying Party integrations use SAML 2.0 to direct users’ web browsers 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.
-
My Page provides SSO to Google Cloud Workforce Identity users leveraging the 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 IDR.
Note: RSA recommends using My Page instead of IDR SSO. At a to-be-determined future date, RSA will announce the end-of-life (EOL) date for the SAML SSO support with IDR. For more information, see Available Now: My Page SSO Enhancements.
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 Google Cloud Workforce Identity using each integration type.
Google Cloud Workforce Identity Integration with CAS
| Authentication Methods | MFA API | RADIUS | SAML | OIDC | ||
| Relying Party | My Page | Relying Party | My Page | |||
| Approve | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| Approve with Code Matching | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| LDAP Password | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| SecurID OTP | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| Authenticate OTP | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| Device Biometrics | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| Device Biometrics with Code Matching | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| SMS OTP | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| Voice OTP | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| FIDO Security Key | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| QR Code | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
| Emergency Access Code | Not tested | Not tested | Supported | Supported | Not tested | Not tested |
Configuration Summary
This section contains instruction steps that show how to integrate Google Cloud Workforce Identity 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 Google Cloud Workforce Identity 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
- Google Cloud Workforce Identity - SAML My Page Configuration - RSA Ready Implementation Guide
- Google Cloud Workforce Identity - SAML Relying Party Configuration – RSA Ready Implementation Guide
- Google Workspace - SAML IDR SSO Configuration - RSA Ready Implementation Guide
RSA Terminology Changes
The following table describes the differences in the terminology 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
Google Cloud Workforce Identity
Known Issues
No known issues.
Related Articles
Google Cloud Workforce Identity - SAML My Page Configuration - RSA Ready Implementation Guide 36Number of Views RSA September 2024 Release Announcements 62Number of Views Delinea - SAML My Page SSO Configuration - RSA Ready Implementation Guide 17Number of Views Microsoft Office 365 - RSA Ready Implementation Guide 329Number of Views CyberArk Password Vault Web Access - SAML My Page SSO Configuration - RSA Ready Implementation Guide 68Number 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 RSA RADIUS Overview Troubleshooting RSA MFA Agent for Microsoft Windows Synchronize Users from Internal Database to Cloud Access Service