UserEcho - SAML Relying Party Configuration - SecurID Access Implementation Guide

This section describes how to integrate SecurID Access with UserEcho using Relying Party. Relying party uses SAML 2.0 to integrate SecurID Access as a SAML Identity Provider (IdP) to UserEcho 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 UserEcho .

Procedure

1. Sign into the Cloud Administration Console and browse to Authentication Clients > Relying Parties and click Add a Relying Party.

   

    

   

    

2. On Basic Information page enter a Name for the application, ie. UserEcho Then click on Next Step.

3. On Authentication page.

   1. select the RSA SecurID Access manages all authentication.

   2. Select the desired Primary Authentication Method from the dropdown list.

   3. Select the desired policy from the Access Policy for Additional Authentication.

   4. Click Next Step.

      

       

4. On Connection Profile page.

   1. Enter the Assertion Consumer Service (ACS) . This is the ACS URL found in your instance of UserEcho . For example https://[ACCOUNT NAME].userecho.com/saml/acs/.

   2. Enter the Service Provider Entity ID. This is the Metadata URL found in your instance of UserEcho . For example https://[ACCOUNT NAME].userecho.com/saml/metadata/.

   3. Click on Download Certificate. This will be used below in the UserEcho configuration.

   4. Click on Choose File and upload the certificate just downloaded.  This same certificate will be used in the UserEcho configuration below.

   5. Open Advanced Configuration section and note the Identity Provider Entity ID field . For Example :https://rsa-blr-pe.auth-demo.securid.com/saml-fe/sso

   6. For User Identity set Identifier Type = Email Address and Property = mail.

   7. Under Attribute Extension section.

   8. Click on +Add.

   9. Add Attribute Name = "Email" and Property = mail.

   10. In Attribute Extension section click +ADD.

   11. Add Attribute Name = "Last name" and Property = sn.

   12. In Attribute Extension section click +ADD.

   13. Add Attribute Name = "First name" and Property = givenName.

   14. Note that the property values may differ in your configuration.

   15. Click on Save and Finish

       

        

5. Browse to Authentication Clients > Relying Parties

6. Scroll down to the your newly created Relying party and click down arrow to Edit and choose View or Download IdP MetatData if you want to save off the metadata information.

   

    

7. 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 UserEcho

Perform these steps to integrate UserEcho with SecurID Access as a Relying Party SAML SP.

Procedure

1. Sign into UserEcho and browse to Agent interface.

2. Navigate to Setup > Integrations > Website > Single sign-on(SAML).

3. Scroll to the SAML settings at the bottom of the page. Note the ACS URL and Metadata URL, this is used above in the CAS configuration. For example, https://mysecurid.userecho.com/saml/acs/ and https://mysecurid.userecho.com/saml/metadata/

4. For SAML SSO URL, enter the Identity Provider URL from the CAS configuration above. For example, https://portal.sso.pe.rsa.net/IdPServlet?idp_id=157mnki28yowd.

5. For X.509 Certificate paste the contents of downloaded certification from step 4c in the CAS configuration above.

6. For Label, choose an appropriate lable for your SAML login button. For example, SecurID.

7. Click on Login Settings. Under External system buttons, scroll down and check the Single sign-on (SAML) checkbox..

8. Click on Save.

Configuration is complete.

Next Step: See main page for more certification information.