This section describes how to integrate RSA SecurID Access with Pega Platform using relying party. Relying party uses SAML 2.0 to integrate RSA SecurID Access as a SAML Identity Provider (IdP) to Pega Platform SAML Service Provider (SP).
Architecture Diagram
Configure RSA Cloud Authentication Service
Perform these steps to configure RSA Cloud Authentication Service as a relying party SAML IdP to Pega Platform .
Procedure
-
Sign into the RSA Cloud Administration Console and browse to Authentication Clients > Relying Parties and click Add a Relying Party.
-
Click the Add a Relying Party button on the My Relying Parties page.
-
From the Relying Party Catalog select the +Add button for Service Provider SAML.
-
Enter a Name for the Service Provider in the Name field on the Basic Information page.
-
Click the Next Step button.
-
On the Authentication page, select RSA SecurID Access manages all authentication.
-
Select your access policy from the Access Policy for Additional Authentication drop-down menu.
-
Select Next Step.
-
For Connection Profile page's Service Provider Metadata section, enter the following information:
-
Assertion Consumer Service (ACS) URL This can be obtained from Step 7 of Configure SAML in Pega Platform section.
-
Service Provider Entity ID - This can also be obtained from Step 7 of Configure SAML in Pega Platform section.
- Select Default Service Provider Entity ID in Audience for SAML Response section.
-
Download Certificate and click Choose File and attach the .PEM file in the configuration.
-
Click Show Advanced Configuration and configure User Identity with the following values:
-
Identity Type – Email Address
-
Property - mail
-
Click Save and Finish.
-
Click Publish Changes
- Navigate to Authentication Clients > Relying Parties and locate Pega in the list and from the Edit option, select View or Download IdP Metadata and Download Metadata File.
Configure SAML in Pega Platform
Perform these steps to configure Pega Platform as a Relying Party SAML SP to RSA Cloud Authentication Service.
Procedure
-
Log onto the Pega Platform Dev Studio.
-
Navigate to Configure > Org &Security > Authentication > Create Authentication Service.
-
Enter the following details:
-
Authentication Type: SAML 2.0
-
Name: Any name for this service
-
Short description: Any short description for this service.
-
-
Click Create and Open.
-
On the Authentication Service form enter a Authentication service alias. This becomes part of the URL of SSO login.
-
Click the Import IDP metadata link and select via file and choose the idp metadata downloaded in Step 15 of Configure RSA Cloud Authentication Service section.
-
After the idp metadata import the Identity Provider (IdP) information should look like this:
-
-
On the Service Provider (SP) settings section, copy the Entity Identification url and Assertion Consumer Service (ACS) location url. These urls are needed in Step 9 of Configure RSA Cloud Authentication Service section.
-
Select Disable request signing checkbox.
-
-
Click Save.
Return to the main page for more certification related information.
Related Articles
Microsoft Entra ID External Authentication Methods (EAM) - Relying Party Configuration Using OIDC - RSA Ready Implementati… 519Number of Views Microsoft Office 365 - SAML Relying Party Configuration - RSA Ready Implementation Guide 252Number of Views Palo Alto NGFW Global Protect - SAML Relying Party Configuration - RSA Ready Implementation Guide 110Number of Views Microsoft Entra ID Custom Controls - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide 193Number of Views Okta - SAML Relying Party Configuration - RSA Ready Implementation Guide 45Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide