Recognize - SAML Relying Party Configuration - SecurID Access Implementation Guide
This section describes how to integrate SecurID Access with Recognize using Relying Party. Relying party uses SAML 2.0 to integrate SecurID Access as a SAML Identity Provider (IdP) to Recognize SAML Service Provider (SP).
Architecture Diagram
Configure SecurID Access Cloud Authentication Service
Perform these steps to configure SecurID Access Cloud Authentication Service as a relying party SAML IdP to Recognize .
Procedure
-
Sign into the Cloud Administration Console and browse to Authentication Clients > Relying Parties and click Add a Relying Party.
-
On Basic Information page enter a Name for the application, ie. Recognize Then click on Next Step.
-
On Authentication page
-
select the RSA SecurID Access manages all authentication
-
Select the desired Primary Authentication Method from the dropdown list.
-
Select the desired policy from the Access Policy for Additional Authentication.
-
Click Next Step
-
-
On Connection Profile page
-
Enter the Assertion Consumer Service (ACS) From the Recognize configuration below for ACS(Consumer) URL For example: https://recognizeapp.com/rsa.com/saml/acs.
-
Enter the Service Provider Entity ID From the Recognize configuration below for Service Provider Metadata url. For example: https://recognizeapp.com/rsa.com/saml/metadata.
-
Open Advanced Configuration section.
- Add Attribute Name = email address and Property = mail
-
Note the Entity ID for the Identity Provider this is needed below for the Recognize configuration
-
Click on Save and Finish
-
-
Browse to Authentication Clients > Relying Parties
-
Scroll down to the your newly created Relying party and click down error next to Edit and choose View or Download IdP MetatData
-
Click on Publish Changes. Your application is now enabled for SSO. If you make any additional changes to the application configuration you will need to republish.
Configure Recognize
Perform these steps to integrate Recognize with SecurID Access as a Relying Party SAML SP.
Procedure
-
Sign into Recognize and browse to Settings > SSO.
-
For Entity ID enter the Issuer Entity ID from SecurID Access CAS noted above.
-
For SSO Target URL enter the Identity Provider URL from CAS noted above.
-
For SLO Target URL enter the Identity Provider URL from CAS noted above.
-
For Certificate use the contents of the metadata XML file downloaded above and copy the X.509 certification information between the tags <ds:X509Certificate></ds:X509Certificate> and paste it in the IDP Certificate field.
-
Note the Service Provider Metadata url value it will be used in the CAS configuration above for Audience.
-
Note the ACS(Consumer) URL value it will be used in the CAS configuration above for the ACS.
-
Save changes.
Configuration is complete.
Next Step: See main page for more certification information.
Related Articles
Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide 718Number of Views Microsoft Office 365 - SAML Relying Party Configuration - RSA Ready Implementation Guide 263Number of Views FortiGate Firewall - SAML Relying Party Configuration Using SSL VPN - RSA Ready Implementation Guide 63Number of Views Fortinet IPsec VPN - SAML Relying Party Configuration – RSA Ready Implementation Guide 10Number of Views Okta - SAML Relying Party Configuration - RSA Ready Implementation Guide 47Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle How to Download and Reinstall the AFX Server Archive in RSA Governance & Lifecycle