Resolving the error "Login failed due to an error with code – SAML_ERR_001. Please reach out to your administrator to resolve this"
Issue description
The error message Login failed due to an error with code – SAML_ERR_001. Please reach out to your administrator to resolve this occurs when ADSelfService Plus receives an invalid, malformed, or incomplete SAML response from the IdP during SSO authentication. This prevents successful user authentication.
Possible causes
Invalid SAML structure: The fundamental XML structure of the SAML response does not conform to SAML specifications.
Incomplete or corrupted SAML response: The SAML response was truncated, altered, or corrupted during transmission.
Generic processing error: ADSelfService Plus encountered an unspecific error when attempting to validate the incoming SAML response.
Mismatched configuration: Discrepancies between the SAML configuration on the identity provider (IdP) and service provider (SP) sides (e.g., incorrect ACS URL, Entity ID, or certificate).
Time synchronization issues: Significant time drift between the IdP and ADSelfService Plus servers can invalidate assertions due to timestamp checks.
Prerequisites
Ensure time synchronization (NTP) between the IdP and ADSelfService Plus servers to prevent validation failures.
Administrator access to both the ADSelfService Plus portal and the IdP configuration interface.
Resolution
Step 1: Check on the IdP side
Review IdP logs: Examine your IdP's logs for any error messages or warnings that occurred during the generation of the SAML assertion for the affected user.
Verify required attributes: Confirm that the SAML response includes all necessary attributes for ADSelfService Plus, such as:
NameID: The unique identifier for the user.
Email address: Often used for user mapping.
UserPrincipalName (UPN): Commonly used in Active Directory environments.
Regenerate IdP metadata: If there have been recent changes to your IdP's configuration (e.g., certificate renewal, endpoint changes), regenerate and export the latest IdP metadata file. This ensures ADSelfService Plus has the latest information.
Step 2: Check on the SP (ADSelfService Plus) side
Verify that ADSelfService Plus is correctly configured to receive and process the SAML response from your IdP.
Log in to ADSelfService Plus with administrator credentials.
Navigate to Admin > Customize > Logon Settings > Single Sign-On.
Verify that the Assertion Consumer Service (ACS) URL and Entity ID displayed match the values configured in your IdP for the ADSelfService Plus application.
If you regenerated the IdP metadata in Step 1, import this new metadata file into ADSelfService Plus. This will automatically update the ACS URL, Entity ID, and certificate.
Click Save to apply the changes and attempt to log in again.
Troubleshooting tips
If the issue persists, consider these advanced debugging techniques:
Use SAML Tracer: Install a browser extension like SAML Tracer to inspect the raw SAML response exchanged between the IdP and SP, helping you identify if it's incomplete, malformed, or missing expected attributes.
SAML binding type: If your SAML response is being sent via HTTP-Redirect binding, very large assertions might exceed URL length limits and be truncated. If supported by your IdP, switch to HTTP-POST binding, which is more robust for larger responses.
Load balancers/proxies: If load balancers, reverse proxies, or web application firewalls are in front of either ADSelfService Plus or your IdP, verify that they are not altering, compressing, or blocking any part of the SAML response in transit.
How to reach support
If the issue persists, contact our support team here.
New to ADSelfService Plus?