Articulate Reach 360 - SAML Relying Party Configuration - RSA Ready Implementation Guide
This article describes how to configure Cloud Access Service (CAS) using SAML Relying Party.
Configure CAS
Perform these steps to configure Articulate Reach 360 as a Relying Party to RSA ID Plus.
Procedure
- Sign in to RSA Cloud Administration Console.
- Select the Authentication Clients > Relying Parties menu item at the top of the page.
- 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 SecurID Access manages all authentication.
- From 2.0 Access Policy for Authentication pulldown select a policy that was previously configured. Click Next Step.
- In the connection profile section, choose Enter Manually for the Data Input Method.
- Navigate to the Service Provider section and enter the following details:
- ACS URL: Provided from Articulate Reach 360 during the configuration.
- Service Provider Entity ID: Provided from Articulate Reach 360 during the configuration.
- In the Message Protection > SAML Response Protection section, select IdP signs assertion within response. Download the certificate by clicking Download Certificate.
- Expand the Show Advanced Configuration section, scroll down to the User Identity section and select the following:
- Identifier Type – Auto Detect.
- Property – Auto Detect.
- In the Statement Attributes section, configure the attributes “email”, “firstName” and “lastName” as these are required by Articulate Reach 360.
- email -> Identity Source -> mail
- firstName -> Identity Source -> giveName
- lastName -> Identity Source -> sn
- In the Identity Provider section and take a note of the Entity ID. This will be used later in Articulate Reach 360 Configuration section.
- Click Save and Finish.
- Click Publish Changes and wait for the operation to be completed.
- After publishing, your application is now enabled for SSO.
The Configuration is complete.
Configure Articulate Reach 360
Perform these steps to configure Articulate Reach 360 with RSA SecurID as a Relying Party.
Procedure
- Log in to your provided tenant with an admin account. https://<Your_org_tenant>.reach360.com
- From the Manage menu, navigate to Settings.
- Go to Single sign-on (SSO) authentication and click Configure SSO.
- On the Configure Single Sign-On (SSO) Authentication page, enter the following details:
- IDP SSO URL: Entity ID obtained in step 14 in the RSA configuration section.
- IDP Issue URI: Entity ID obtained in step 14 in the RSA configuration section.
- IDP Signature Certificate: Copy and paste the downloaded certificate in step 11 in the RSA configuration section.
- Response Signature Verification: Choose Assertion from the dropdown menu to match the signing of RSA of the assertion.
- Click Save & Continue to SAML Info.
- On the Your Reach 360 SAML Information page, copy the Assertion Consumer Service URL and Audience URI, the 2 values will be used in their respective fields in step 10 in the RSA configuration section.
- Click Done. SSO is now configured on Articulate Reach 360 side.
The Configuration is complete.
Related Articles
Articulate Reach 360 - SCIM Client Configuration - RSA Ready Implementation Guide 13Number of Views Articulate Reach 360 - SAML My Page SSO Configuration - RSA Ready Implementation Guide 26Number of Views How can I change the On-Demand Authentication (ODA) PIN for my RSA Community account? 112Number of Views Unable to check NTP status using ntpq -p command on RSA Authentication Manager 8.x 1.6KNumber of Views What happens when you reach the license limit of RSA Authentication Manager? 1.24KNumber of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?