Transformation Engine next working as expected with SecurePortal / TSSO

Follow
    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  All

    Description:  

    A realm using the transformation engine works perfectly fine and then, once Transparent SSO or SecurePortal is enabled, it seems to stop working or become intermittent 

    Cause:  

    The way the user is authenticated can stop TE setting on the Authenticated User attribute from working. 

     

    Resolution:  

    1. Look at the Datatab to workout which attributes are not in use for this realm. Pick one that isn't checked as writable

    2. Move your TE settings to the attribute that isn't currently in use.

    Eg: If, for example, the XSLT currently has this entry

    <UserID>
    <xsl:value-of select="user:UpperCase(user/UserID)"/>
    </UserID>

    swap it to

    <Phone4>
    <xsl:value-of select="user:UpperCase(user/UserID)"/>
    </Phone4>

    3. Notice how the value of select is the same, we're just inserting the Authenticated User ID into the Phone4.

    4. Update the UserID Mapping/SAML claims that currently use Authenticated User ID to use the new profile field. In our example this was Phone4.

    5. Save your changes. 

     

     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.