Tehama - SAML Relying Party Configuration - SecurID Access Implementation Guide

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

Procedure

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

   

    

   

    

2. On Basic Information page enter a Name for the application, ie. Tehama 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. Under the Service Provider Metadata section.

      

       

   2. Enter the Assertion Consumer Service (ACS) . Enter the value for the Callback URL copied from in the Tehama configuration. This is based on the Name of your Tehama instance. The URL is in the form of https://<Instance>.tehama.io/saml/login/callback. For example, https://mycompany.tehama.io/saml/login/callback.

   3. Enter the Service Provider Entity ID. Enter the value for the Entity ID copied from in the Tehama configuration. This is based on the Name of your Tehama instance. The URL is in the form of https://<Instance>.tehama.io. For example, https://mycompany.tehama.io.

   4. Uncheck SP signs SAML Requests.

   5. Click on Download Certificate. This will be used below in the Tehama configuration.

   6. Click on Choose File and upload the certificate just downloaded.  This same certificate may be used in the Tehama configuration below.

   7. Open Advanced Configuration section

      

       

   8. For Identifier Type Email Address choose mail for the Property.

   9. Under Attribute Extension click on +Add.

   10. For Attribute Name enter email for Property choose mail.

   11. Under Attribute Extension click on +Add.

   12. For Attribute Name enter firstName for Property choose givenName.

   13. Under Attribute Extension click on +Add.

   14. For Attribute Name enter lastName for Property choose sn.

   15. Note the Identity Provider Entity ID field . For Example :https://rsa-inst-pe.auth-demo.securid.com/saml-fe/sso.

5. Click on Save and Finish.

6. Browse to Authentication Clients > Relying Parties

7. 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 to be used in the Tehama configuration below.

   

    

8. 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 Tehama

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

Procedure

1. Sign into Tehama and select  Organization and click on Authentication.

2. Check the Enable SAML Single-Sign on checkbox.

3. Copy the Entity ID this is used in the configuration details needed for SecurID configuration.

4. Copy the Callback URL (Assertion Consumer Service URL) this is used in the configuration details needed for SecurID configuration.

5. For Federation Metadata XML copy and paste the contents exported IDP Metadata saved above during SecurID CAS configuration.

   

    

6. For User Provisioning section select the Method as SAML and configure the attributes that map to the configuration with SecurID Access CAS configuration above. For example:

   1. Email: email.

   2. First Name: firstName.

   3. Last Name: lastName.

7. Click on Save.

Configuration is complete.

Next Step: See main page for more certification information.