Intercom - SAML Relying Party Configuration - SecurID Access Implementation Guide
This section describes how to integrate SecurID Access with Intercom using Relying Party. Relying party uses SAML 2.0 to integrate SecurID Access as a SAML Identity Provider (IdP) to Intercom SAML Service Provider (SP).
Architecture Diagram
Configure SecurID Access Cloud Authentication Service
Perform these steps to configure SecurID Access Cloud Authentication Service(CAS) as a relying party SAML IdP to Intercom .
Procedure
-
Sign into the Cloud Administration Console and browse to Authentication Clients > Relying Parties and click Add a Relying Party. Then select Add for a SAML service provider.
-
On Basic Information page enter a Name for the application, ie. Intercom 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.
-
Under the Service Provider Metadata section.
-
For the Assertion Consumer Service (ACS) enter the documented value for SAML name for this workspace from Intercom. This URL is based on the SAML name, https://app.intercom.com/saml/<SAML_NAME>/consume. For example, https://app.intercom.com/saml/z6d2test/consume.
-
For the Service Provider Entity ID enter the documented value for SAML name for this workspace from Intercom. This URL is based on the SAML name, https://app.intercom.com/saml/<SAML_NAME>. For example, https://app.intercom.com/saml/z6d2test.
-
Check SP signs SAML Requests.
-
Upload the Intercom SP certificate. Go to the Intercom SSO documentation. Under Encryption AES256_CBC with this certificate. Copy and paste the certificate including BEGIN/END comments into a file and save. Then click on Choose File and upload the certificate file you just created.
-
Check IdP signs assertion within response.
-
Click on Download Certificate. This will be used below in the Intercom configuration.
-
Open Advanced Configuration section.
-
For Identifier Type Email Address choose mail for the Property.
-
For Attribute Extension click +Add.
-
For Attribute Name enter lastName and select corresponding Property , i.e. sn.
-
Click +Add.
-
For Attribute Name enter firstName and select corresponding Property , i.e. givenName.
-
Note the Identity Provider Entity ID field . For Example :https://rsa-test-pe.auth-demo.securid.com/saml-fe/sso.
-
-
Click on Save and Finish.
-
Browse to Authentication Clients > Relying Parties .
-
Scroll down to the your newly created Relying party and click down arrow to Edit and choose View or Download IdP MetatData and save off the metadata information if desired.
-
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 Intercom
Perform these steps to integrate Intercom with SecurID Access as a Relying Party SAML SP.
Procedure
-
Login into Intercom as an administrator with email in the same domain that SSO is being configured with.
-
Click on User account icon and choose Settings.
-
From Security choose Security Settings.
-
Scroll down to the Authentication methods section and select Require SAML SSO.
-
First configure allowed domains if not done so.
-
Type in your domain and click on Add domain.
-
If first time, verify the domain, a pop up will give the required information to validate the domain. It may take some time for the domain to be validated.
-
Once a domain has been invalided it will appear in the list off allowed domains above the text field.
-
Note the SAML name for this workspace. This string represents the instance name needed to configure the Service Provider information in the SecurID CAS configuration.
-
For Identity provider Single Sign-On URL provide the Identity Provider Entity ID from the above in the SecurID CAS configuration. For example, https://rsa-test-pe.auth-demo.securid.com/saml-fe/sso. Note the https:// part of the string is not needed
-
For Single Sign On x509 Certificate copy and paste the certificate downloaded above in the SecurID CAS configuration.
-
Click on Save .
-
A pop up will appear test the configuration. Click on the Authenticate with identity Provider and authenticate the user same logged into Intercom via SecurID Cloud Authentication service.
Configuration is complete.
Next Step: See main page for more certification information.
Related Articles
Microsoft Entra ID External Authentication Methods (EAM) - Relying Party Configuration Using OIDC - RSA Ready Implementati… 499Number of Views GoToMeeting - SAML Relying Party Configuration - RSA Ready Implementation Guide 14Number of Views Dropbox - SAML Relying Party Configuration - RSA Ready Implementation Guide 8Number of Views PingFederate - Relying Party Configuration Using SAML - RSA Ready Implementation Guide 196Number of Views Microsoft Office 365 - SAML Relying Party Configuration - RSA Ready Implementation Guide 233Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x