Terminus - SAML Relying Party Configuration - SecurID Access Implementation Guide
This section describes how to integrate SecurID Access with Terminus using Relying Party. Relying party uses SAML 2.0 to integrate SecurID Access as a SAML Identity Provider (IdP) to Terminus 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 Terminus .
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. Terminus 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.
-
Enter the Assertion Consumer Service (ACS) . Enter the value for the Assertion Consumer Service (ACS) URL from the Terminus configuration. For example, https://app.terminusapp.com/auth/saml/callback?uid=acct_QaprrsFnw3.
-
Enter the Service Provider Entity ID. Enter the value for the Service Provider Entity ID from the Terminus configuration.For example, https://app.terminusapp.com/acct_QaprrsFnw3.
-
Click on Download Certificate. This will be used below in the Terminus configuration.
-
Click on Choose File and upload the certificate just downloaded. This same certificate may be used in the Terminus configuration below.
-
Open Advanced Configuration section.
' -
For Identifier Type Email Address choose mail for the Property.
-
Note the Identity Provider Entity ID field . For Example :https://rsa-inst-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 Terminus
Perform these steps to integrate Terminus with SecurID Access as a Relying Party SAML SP.
Procedure
-
Sign into Terminus and select Account Name click on Account Setttings .
-
Click on Single Sign On tab.
-
In the Configure this in your Identity Provider section note the following.
-
Assertion Consumer Service (ACS) URL. For example, https://app.terminusapp.com/auth/saml/callback?uid=acct_QaprrsFnw3.
-
Service Provider Entity ID. For example, https://app.terminusapp.com/acct_QaprrsFnw3.
-
-
Select the Enable SAML SSO checkbox.
-
For Identity Provider Single Sign-On URL or SAML 2.0 Endpoint copy the Identity Provider Entity ID from the above in the SecurID CAS configuration. For example, https://my-rsa-securid.auth-demo.securid.com/saml-fe/sso.
-
For SSO Identity Provider Certificate Copy and paste the contents of the certificate saved above in the SecurID CAS configuration.
-
Click on Save.
Configuration is complete.
Next Step: See main page for more certification information.
Related Articles
Snowflake-integration-configuration-relying-party 2Number of Views Bugsnag-integration-configuration-relying-party 1Number of Views How to use any client certificate as an Administrator in another KCA installation? 6Number of Views Unable to use Administrators Client SSL Certificate 19Number of Views Shufflrr - SAML Relying Party Configuration - SecurID Access Implementation Guide 1Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … RSA Authentication Manager 8.9 Release Notes (January 2026)