Users encounter an "Access Denied" error or authentication failure when logging into Spectrum OneClick via SAML SSO.
In some cases, the system creates users with email addresses instead of the expected User ID, or fails to create new users based on group memberships when using Microsoft Entra ID (formerly Azure AD) as the Identity Provider (IdP).
The following errors appear in the OneClick stdout.log or SAML debug logs:
WARN com.aprisma.errorlog - Unable to obtain user attributes DEBUG com.aprisma.tomcat.realm.SecurityRealm - securitySp.getUserRoles returned null ERROR com.aprisma.tomcat.authenticator.Saml2FederationAuthenticator - No SAML groups found in Spectrum ERROR com.aprisma.tomcat.authenticator.Saml2FederationAuthenticator - SAML user #### authentication failed.
Additionally, the SAMLTokenValidator may show attributes being received with long schema URLs (e.g., http://schemas.xmlsoap.org/ws/2005/05/identity/claims/memberOf) which prevent correct mapping.
This issue occurs when the Identity Provider (IdP) is not configured to send the specific attribute names that DX Spectrum requires.
Spectrum expects the username in the primary NameID element and user groups in an attribute specifically named memberOf.
If Entra ID sends the email address in NameID or uses a long URI for the group claim, authentication fails.
To resolve this, you must adjust the SAML mapping rules within the Microsoft Entra ID Enterprise Application settings:
user.onpremisessamaccountname or user.employeeid) rather than the email address.sAMAccountName.memberOf. Do not include a namespace or URL.If you continue to experience issues, verify that the group names received from Entra ID match the group names created in Spectrum OneClick exactly (case-sensitive).
For further assistance, see . Scroll to the bottom of the page and click on your respective region.