Troubleshooting: Access Token's "sub" Claim Does Not Show the Expected Attribute – SecureAuth Support

Version Affected: All

Overview

In SecureAuth CIAM, an access token's sub claim shows a value other than the email address, even though the Workspace appears to be mapped to email.

Cause

The Workspace's Subject Identifier is set to a subject format other than the custom Email attribute, so the sub claim is populated from a different source.

Resolution:

To resolve this:

In the Workspace, go to OAuth > Tokens.
Select the Subject Identifier tab.
Under Subject format, select Custom.
Set Custom Subject Attribute to Email.
Select Save.

The Tokens page's Subject Identifier tab in a CloudEntity Workspace, with Custom selected as the Subject format and Custom Subject Attribute set to Email.

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.