Why does "User Login failed 216" error appear after SSO integration method changed from Azure AD to SAML?
Issue Description
After changing the SSO Integration from Azure AD to SAML, the "User Login failed 216" error is thrown, but Azure AD works fine.
Resolution
On verification, it is found that the SAML configuration is using the user.name but, as per the documentation, the value passed in the prioritized claim is used by UiPath as a unique identifier and it is used to link any existing local users (the local user's email address) to this directory user in Azure AD.
For a smooth switch between Azure AD and SAML directory integration, it is recommended to pass in both of these claims with the appropriate user values, so update the user.mail as value in Unique User Identifier (Name ID). Refer the below screenshot to make changes:
Follow the steps below:
- Sign in to the UiPath - Microsoft Entra admin center as at least a Cloud Application Administrator.
- Browse to "Identity" > "Applications" > "Enterprise applications" > "All applications".
- Select the application, select "Single sign-on" in the left-hand menu, and then select "Edit" in the "Attributes & Claims" section.
- Update the user.mail as value in Unique User Identifier (Name ID).