Documo - SAML Relying Party Configuration - RSA Ready SecurID Access Implementation Guide
This section describes how to integrate RSA SecurID Access with Documo using Relying Party. Relying party uses SAML 2.0 to integrate RSA SecurID Access as a SAML Identity Provider (IdP) to Documo 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 Documo .
Procedure
-
Sign into the RSA 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. Documo 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 Documo configuration below for Assertion Consumer Service. For example: https://api.documo.com/assert.
-
Enter the Service Provider Entity ID From the Documo configuration below for Entity Descriptor. For example: https://api.documo.com.
-
Open Advanced Configuration section.
- Add Attribute Name = email and Property = mail.
- Note the Entity ID for the Identity Provider. This will be needed for the Documo configuration below.
-
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 and download the Metadata File.
-
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 Documo
Perform these steps to integrate Documo with RSA SecurID Access as a Relying Party SAML SP.
Procedure
-
Sign into Documo and browse to Account Settings > Security.
-
Scroll down to SSO and select Download Metadata.
-
In the Metadata file, locate the values for the Assertion Consumer Service and Entity Descriptor tags. These values will be used for the RSA Cloud Authenitcation Service (CAS) configuration above.
-
For the SSO URL enter the Entity ID from the RSA configuration above. For example, https://rsa-blr-pe.auth-demo.securid.com/saml-fe/sso.
- For the Entity id enter the Entity ID from the RSA configuration above. For example, https://rsa-blr-pe.auth-demo.securid.com/saml-fe/sso.
- For Email domain, enter the email domain for your SSO. For example, mycompany.com.
- For the Signer Certficate enter the cert.pem file downloaded from the generated certificate bundle in the RSA Cloud Authenitcation Service (CAS) configuration.
- In the Field Name in the SAML token containing the Identity email, enter email.
-
Click Submit.
Configuration is complete.
See main page for more certification information.
Related Articles
Palo Alto NGFW Global Protect - SAML Relying Party Configuration - RSA Ready Implementation Guide 110Number of Views Microsoft Office 365 - SAML Relying Party Configuration - RSA Ready Implementation Guide 243Number of Views Workday - SAML Relying Party Configuration - RSA Ready Implementation Guide 4Number of Views Okta - SAML Relying Party Configuration - RSA Ready Implementation Guide 45Number of Views Microsoft Entra ID External Authentication Methods (EAM) - Relying Party Configuration Using OIDC - RSA Ready Implementati… 502Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Connection fails to Cloud Authentication Service when connecting through a proxy server from RSA Authentication Manager to…