000033795 - AuthRequest asking for a transient ID in SAML SSO integration in RSA Via Lifecycle and Governance

Document created by RSA Customer Support Employee on Jan 3, 2017Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000033795
Applies ToRSA Product Set: Identity Governance and Lifecycle
RSA Version/Condition: 7.0
IssueWhen implementing Security Assertion Markup Language (SAML) Single Sign On (SSO) integration in RSA Via Lifecycle and Governance since the SAMLRequest is based on the "SAML-2.0-NameID-Transient" profile, the SAMLResponse will be 'transient' with the random number in the NameID field which will never match the identity column value in T_Master_Enterprise_User Table, resulting in the failure of SSO.
Below is the NameID format:
<saml2p:NameIDPolicy AllowCreate="true" Format="urn:oasis:names:tc:SAML:2.0:nameid-format:transient" />

 
ResolutionTo resolve the issue, follow the steps below.
  1. Log into the RSA Via Lifecycle and Governance User Interface.
  2. Navigate to Admin > System and click on the Authentication tab. 
  3. Select the SSO Authentication Source.
  4. Update the "SAMLAuthenticatorClass" value com.aveksa.server.authentication.SAMLPINGAuthenticatorImpl. By default the value is set as com.aveksa.server.authentication.SAMLAuthenticatorImpl.
  5. Restart the application.
  6. After restart, the SAMLRequest will be build on the correct profile and will create a SAMLResponse with the UnifiedUserColumn value into the NameID field.
Below is an example USER_ID using the configuration described above.
User-added image
NotesSAMLPingAuthenticatorImpl class in the source code, has the function to generate the NameID policy based on 'urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified' 
Please make sure that the Identity Provider (IdP) set by Customer in a nameid-format. RSA Via Lifecycle and Governance code looks at that, parses the nameid and locates it in the T_Master_Enterprise_User Table. If the user is there (and not terminated or disabled), it returns as an authentication success.

Attachments

    Outcomes