Certified: September 01, 2026

Solution Summary

This guide describes Cisco ISE integration with RSA using SAML 2.0, RADIUS, and Authentication Agent. Use this information to determine which use case and integration type your deployment will employ.

Use Case

Cisco ISE can be integrated with RSA using SAML Relying Party, SAML My Page, RADIUS, and Authentication Agent. When integrated, users must authenticate with RSA to sign in to Cisco ISE. 
      

Integration Types

RADIUS integrations provide a text-driven interface for RSA within the partner application. RADIUS provides support for most RSA authentication methods and flows.

Authentication Agent integrations use an embedded RSA agent to provide RSA Authentication Manager (AM) and Authenticate OTP authentication methods within the partner’s application. Authentication agents are simple to configure and support the highest rate of authentications.

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

Cisco ISE Integration with CAS

Cisco ISE Integration with AM

Configuration Summary

This section contains instruction steps that show how to integrate Cisco ISE 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 Cisco ISE 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

• Cisco ISE - SAML My Page Configuration - RSA Ready Implementation Guide
• Cisco ISE - SAML Relying Party Configuration - RSA Ready Implementation Guide
• Cisco ISE 3.2 - RADIUS Configuration - RSA Ready Implementation Guide

AM

• Cisco ISE 3.4 - Authentication Agent Configuration - RSA Ready Implementation Guide
• Cisco ISE 3.2 - RADIUS Configuration - RSA Ready Implementation Guide
• Cisco ISE 3.2 - IPV6 Configuration - RSA Ready Implementation Guide.

Use Case Configuration

Cisco ISE provides several user-facing portals that can leverage SAML authentication through CAS. After completing the SAML integration described in this guide, the configured CAS Identity Provider can be assigned to one or more Cisco ISE portals, enabling centralized authentication and multifactor authentication for portal users.
This section describes the Cisco ISE portal types supported by the integration and the additional portal-specific configuration required to enable SAML authentication. While the SAML trust relationship between Cisco ISE and CAS remains the same, the steps required to apply the configuration may vary depending on the portal being protected.

  
Note: For every Cisco ISE use case, each portal is treated as a separate or new Service Provider. So a separate Application/Relying party is needed on the RSA side, and a corresponding new Identity Provider entity in Cisco ISE since each portal has its own metadata to be used in RSA.

• Cisco ISE - My Devices Portal Configuration - RSA Ready Implementation Guide
• Cisco ISE - Sponsor Portal Configuration - RSA Ready Implementation Guide
• Cisco ISE - Self-Registered Guest Portal Configuration - RSA Ready Implementation Guide
• Cisco ISE - Sponsored Guest Portal Configuration - RSA Ready Implementation Guide
• Cisco ISE - Certificate Provisioning Portal Configuration - RSA Ready Implementation Guide
• Cisco ISE - Admin Access 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

AM 8.7 Patch 1, Virtual Appliance or later

Cisco ISE 3.5

Known Issues

No known issues.