000039158 - How to implement SAML SSO Authentication with Microsoft Azure Active Directory and RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jul 23, 2020Last modified by RSA Customer Support Employee on Jul 23, 2020
Version 7Show Document
  • View in full screen mode

Article Content

Article Number000039158
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1, 7.2.0
 
IssueRSA Identity Governance & Lifecycle supports using an external SAML SSO source as the IDP for authentication. This RSA Knowledge Base Article describes how to configure Microsoft Azure Active Directory Identity Source as an Identity Provider (IDP) for SAML authentication with RSA Identity Governance & Lifecyle as the Service Provider (SP).
 
ResolutionTo configure Microsoft Azure Active Directory as an IDP for SAML authentication with RSA Identity Governance & Lifecyle, follow the steps below:


Configure Microsoft Azure



  1. Log into the Microsoft Azure portal as an administrator.
  2. Select Azure Active Directory from the left-hand menu.
  3. Select Enterprise Applications from the left-hand menu.
  4. Click the New Application button and define a new application.

The new application should be of type Non-gallery application.

User-added image



  1. Choose a name such as RSA Identity Governance & Lifecycle.
  2. After the application has been created, select the new application RSA Identity Governance & Lifecycle in the Enterprise applications | All Applications menu.
  3. Select single sign-on from the left-hand menu.
  4. Under Basic SAML Configuration: 

  1. AveksaURL - Enter a valid URL for the Reply URL (Assertion Consumer Service URL). This must be the URL ending in /aveksa/main for the hostname (not IP address) and port for the RSA Identity Governance & Lifecycle server. If you are using a proxy or load balancer, the name and port must be the one used by external parties to access the site.
  2. Enter a value for Identifier (Entity ID). This may be any unique value but it is recommended that this be the same URL string used above.
  3. Enter a value for Sign on URL.This may be any unique value but it is recommended that this be the same URL string used above. 

User-added image


  1. Under User Attributes & Claims click the Edit icon.

Under Additional Claims:


  1. Identify the Claim name that exactly matches http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name.
  2. Click on this entry to edit it. 

User-added image



  1. Identify a Microsoft AD User attribute that meets the following conditions.

  • Uniquely identifies the Microsoft AD user.
  • Is collected by the RSA Identity Governance & Lifecycle Identity Collector.
  • Uniquely matches the RSA Identity Governance & Lifecyle user to the Microsoft AD user. 

  1. UnifiedUserColumn - Identify a column in the RSA Identity & Governance T_MASTER_ENTERPRISE_USERS table that

  • Uniquely identifies the RSA Identity Governance & Lifecycle user.
  • Is collected by the RSA Identity Governance & Lifecycle Identity Collector.
  • Uniquely matches the Microsoft AD user to the RSA Identity Governance & Lifecycle user.

Most likely the AD attribute will be user.onpremiseaccountname and most likely this will match to the RSA Identity Governance & Lifecycle USER_ID column.



  1. Edit the Source attribute.
  2. From the pull down menu select the Microsoft AD User attribute you have chosen. 

User-added image



Do not edit anything else on this screen.



  1. Click Save.

It is not necessary to make any other changes to the User Attributes & Claims section. Other attributes including the Required Claim attribute are ignored by RSA Identity Governance & Lifecycle. 



  1. Under SAML Signing Certificate:

IDP Certificate - Click the Download link for the Certificate (Base64) and save this file for use in a subsequent step.



User-added image



  1. Under Setup RSA Identity Governance & Lifecycle:

IdentityURL- Copy the Login URL for use in a subsequent step.



User-added image




Configure RSA Identity Governance & Lifecycle 



  1. In the RSA Identity Governance & Lifecycle user interface go to Admin > System > Authentication tab.
  2. Click Create Authentication Source

CAUTION: After creating or editing an Authentication Source, the RSA Identity Governance & Lifecycle server will need to be restarted for the changes to take effect. Note that if the authentication source is not functional and provisioning has not been made for an alternative authentication source, access to the server may not be possible.



  1. Select an authentication source name and choose the authentication type SSO SAML from the drown-down menu. 
  2. Click Next. This brings you to the Configuration Information screen.
  3. Enter a value for the UnfiedUserColumn. This should be the value decided upon in section 9d above. Typically this should be USER_ID.
  4. Enter a value for the IdentityURL.This should be the URL saved in section 11 above.   
  5. Accept the default value for SAMLAuthenticatorClass of com.aveksa.server.authentication.SAMLAuthenticatorImpl.
  6. Optionally (not required) enter a LogOffURL.  
  7. Enter the AveksaURL. This should be identical to the value used in section 8a above.
  8. For the IDP Certificate click the Choose File button and select the certificate file saved in section 10 above.

User-added image



  1. Click Finish.

 
Notes
  • Microsoft Azure does not validate the RSA Identity Governance & Lifecycle Certificate.
  • For troubleshooting you can:
    • Use the Azure Test this application feature.
    • Use the Chrome Extension SAMLChrome Panel to examine the SAML request and response.
    • Enable DEBUG logging for the com.aveksa.server.authentication class. (Admin > Diagnostics > Logs tab.)

 

Attachments

    Outcomes