Certified: July 28, 2026

Solution Summary

This guide describes integrating Okta with RSA using SAML 2.0. Use this information to determine which use case and integration type your deployment will employ.

Use Case

Okta can be integrated with RSA using SAML My Page SSO, Relying Party, and as a SCIM client. When integrated, users must authenticate with RSA to sign in to Okta. 
      

Integration Types

My Page SSO provides Single-Sign-On (SSO) to Okta 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 Okta users’ web browsers to be automatically redirected to Cloud Access Service (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.

SCIM: Okta will serve as the SCIM client with CAS acting as a SCIM server, providing an endpoint for the SCIM client to connect to.

   
This integration will allow the administrators of Okta to synchronize any changes performed to Okta with the Unified Directory of CAS. Any CRUD operations (create, read, update, and delete) done on the users on the Okta side will automatically synchronize to the CAS without any manual intervention needed from the administrator side.
           

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 Okta using each integration type.

Okta Integration with CAS

Okta Integration with RSA Authentication Manager (AM)

Configuration Summary

This section contains instruction steps that show how to integrate Okta 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 Okta 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 Relying Party
• SAML My Page SSO
• SAML Relying Party as a step up for Okta applications 
• Okta - SCIM Configuration - 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. 

Certification Details

CAS

Okta

Known Issues

No known issues