Announcements

SecurID® Integrations

Blocks Edit - SAML Relying Party Configuration - RSA Ready SecurID Access Implementation Guide

Blocks Edit - SAML Relying Party Configuration - RSA Ready SecurID Access Implementation Guide

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

Architecture Diagram

kotlad1_0-1628775202030.png

 

Configure RSA Cloud Authentication Service

Perform these steps to configure RSA Cloud Authentication Service as a relying party SAML IdP to Blocks Edit .

Procedure

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

    2. Click on +Add for Service Provider SAML.

kotlad1_1-1628775294188.png

 

kotlad1_2-1628775341150.png

 

  1. On Basic Information page enter a Name for the application, ie. Blocks Edit Then click on Next Step.

  2. On Authentication page.

      1. select the RSA SecurID Access manages all authentication

      2. Select the desired Primary Authentication Method from the dropdown list. i.e Password.

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

      4. Click Next Step

    kotlad1_3-1628775390320.png

     

  3. On Connection Profile page.

      1. Enter the Assertion Consumer Service (ACS) with the Single sign on URL from the Blocks Edit configuration. For example, https://580.app.blocksedit.com/sso.

      2. Enter the Service Provider Entity ID with the Entity ID from the Blocks Edit configuration. For example, https://sso.blocksedit.com.

      3. Under Audience for SAML Response ensure Default is selected.

      4. Under Message Protection click on the Download Certificate. The certificate will be used in the Blocks Edit configuration below.

      5. Uncheck the SP signs SAML requests.

      6. For IdP signs ensure Assertion within Response is selected.

      7. Open Advanced Configuration section

      8. Under Attribute extension

      9. Add Attribute Name = firstName and Property = givenName.

      10. Add Attribute Name = lastName and Property = sn.

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

      12. Click on Save and Finish.

    kotlad1_4-1628775442209.png

     

  4. Browse to Authentication Clients > Relying Parties Next to the Blocks Edit configuration select View or Download IdP Metadata from the Edit button. The metadata file may be used in the Blocks Edit configuration below.

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

    kotlad1_5-1628775476756.png

 

Configure Blocks Edit

Perform these steps to integrate Blocks Edit with RSA SecurID Access as a SAML SSO Agent.

Procedure

  1. Sign into Blocks Edit as Admin and browse ProfileMy Account.

  2. Scroll down to Integrations and click on Add adjacent to Single Sign-On.

  3. For Name enter an name.

  4. For Identity Provider select Custom.

  5. Under Service provider SAML section note the Entity ID and Single sign on URL. These are used above in the CAS configuration.

  6. Under Identity provider SAML section enter for the Entity ID field enter the value for the Identity Provider Entity ID obtained above. For example, https://rsa-blr-pe.auth-demo.securid.com/saml-fe/sso.

  7. For the Single sign on URL field enter the value for the Identity Provider Entity ID obtained above. For example, https://rsa-blr-pe.auth-demo.securid.com/saml-fe/sso

  8. For the X.509 Certificate upload the certificate downloaded in the Replying Party configuration for RSA Cloud Authentication Service (CAS) above.

  9. Click on Save Settings.

  10. See main page for more certification information.

No ratings
Version history
Last update:
‎2021-08-18 11:35 AM
Updated by:
Article Dashboard