

There isn't a User with that ID Property, but there is a user with the exact email address as their Username. Example: The ID Property is an email address.Example: The ID Property is not a username however, the username requested is not available.The following required fields (Username, FirstName, LastName, Department, etc.) are used as the ID Property.This error is generic and can mean any of the following: If user provisioning is ENABLED (Error reads: We apologize there was an error with the username) If the user already exists in the LMS, change the ID Property in the Absorb side configuration to match your Identify Providers in the Name ID Property of the SAML Response.If the user doesn't exist in the LMS, create the account.If user provisioning is DISABLED (Error reads: We apologize no matching Absorb user was found): HTTP Code: 302 302: No Matching User Found or There was an Error with Username HTTP Code: 302 - No Matching User FoundĪbsorb Login Screen "We apologize no matching Absorb user was found, or there was an error with the username"Īfter Authenticating with the SSO provider, the User selects the App on the SSO portal and is routed to the Absorb dashboard with an error. The user must be Active in the LMS for them to successfully log in. The user attempting to log in is Inactive in the LMS. The Logout URL must begin with 200: Invalid or Not Found Credentials HTTP Code: 200 -Invalid or not found credentialsĪbsorb Dashboard Message: Invalid or not found credentials The Single Logout URL is invalid in the SSO Settings. However, a grey screen is seen with three dots, and the page never loads. The Login shows as Successful in the Logins table, and the learner is taken to one of the following error pages:
MICROSOFT ERROR REPORTING LOG VERSION 2.0ERROR SIGNATURE CODE
In the above issue, there were users with the same email address under Inactive and Active users.Ģ00: Code after Successful Log In HTTP Code: 200 - 200 after successful login Remove or edit users that have the same unique identifier. When clicking the Absorb LMS app in the SSO portal, the user receives the above message. HTTP Code: 200 200: Multiple Users HTTP Code: 200 - Multiple UsersĪbsorb Dashboard Message: "We apologize multiple users were found matching the NameID assertion."

This must match what your identity provider is sending as the NameId value in the SAML Response to match to a user in the LMS using the Id Property as defined in your SSO configuration settings within Absorb.Ī route must be assigned to the SSO configuration in the LMS otherwise, the SSO configuration will not activate.įor Identity Provider Initiated configurations, if relay states are desired, this option must be enabled through your SSO provider, or they will be ignored upon successful authentication. Make sure that there are no line breaks or spaces in the key when it is entered to Absorb this should exactly match what is in the SAML Response.

