ITBoost-integration-configuration-relying-party
2 years ago
Originally Published: 2021-10-27

ITBoost - SAML Relying Party Configuration - SecurID Access Implementation Guide

This section describes how to integrate SecurID Access with ITBoost using Relying Party. Relying party uses SAML 2.0 to integrate SecurID Access as a SAML Identity Provider (IdP) to ITBoost SAML Service Provider (SP).

Architecture Diagram

gmoison_0-1635426695595.png

 

Configure SecurID Access Cloud Authentication Service

Perform these steps to configure SecurID Access Cloud Authentication Service(CAS) as a relying party SAML IdP to ITBoost .

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.

    gmoison_1-1635426750491.png

     

    gmoison_2-1635426786261.png

     

  2. On Basic Information page enter a Name for the application, ie. ITBoost 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.

      gmoison_3-1635426810247.png

       

  4. On Connection Profile page.

    1. Under the Service Provider Metadata section.

      gmoison_4-1635426833941.png

       

    2. Enter the Assertion Consumer Service (ACS) . Enter the value for the Reply URL copied from in the ITBoost configuration. For example, https://v4-api-na.itboost.com/users/sso-assert.

    3. Enter the Service Provider Entity ID. Enter the value for the Identity Provider Entity ID copied in step h. below. For example, https://rsa-securidtest-pe.securid.com/saml-fe/sso/sp_entity_id.

    4. Uncheck SP signs SAML Requests.

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

    6. Open Advanced Configuration section

      gmoison_5-1635426859844.png

       

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

    8. Add a Discrimator, for example "sp_entity_id" and then copy Identity Provider Entity ID field . For Example, /https://rsa-securidtest-pe.securid.com/saml-fe/sso/sp_entity_id.

  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 ITBoost configuration below.

    gmoison_6-1635426886166.png

     

  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.

    gmoison_7-1635426927006.png

     

 

Configure ITBoost

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

Procedure

  1. Sign into ITBoost and select Settings .

  2. Click on Organization Settings and under Admin Dashboard select on Advanced Settings.

  3. Select Login Methods.

  4. Under Enforce Login section select SSO.

  5. Under IDP ID section select other.

  6. Note the Reply URL and SP Metadata URL for this configuration. These values are used above in the SecurID Access Configuration.

  7. For LOGIN URL enter the Identity Provider Entity ID from the SecurID Access Configuration above. For example, https://rsa-securidtest-pe.securid.com/saml-fe/sso/sp_entity_id.

  8. For EntityID enter the Identity Provider Entity ID from the SecurID Access Configuration above. For example, https://rsa-securidtest-pe.securid.com/saml-fe/sso/sp_entity_id.

  9. For LOGOUT URL enter the enter the domain URL for your ITBoost instance. For example, https://myinst.itboost.com.

  10. For CERTIFICATE Cut and paste the contents of the certificate downloaded from the SecurID Access Configuration above.

  11. Save changes.

Configuration is complete.

Next Step: See main page for more certification information.