SMAL authenticatio

Question

Hi Team, 
 I recently configured SAML in Appian, and when some existing users attempted to access Appian via SSO, they encountered a 401 error. I had already added these users to the authentication group, and ensured that the Identity Provider (IdP) username was in lowercase, with both the username and email matching. However, the 401 error still occurred. 
 As a temporary workaround, I changed the username, and when the old user tried to access Appian through SSO, Appian treated the user as new. As a result, the user was recreated because we have the "Create new users upon sign-in" option enabled in the SAML settings. 
 Since we cannot change the username for all users, I am looking for a solution to resolve this issue without modifying usernames. Any help with addressing this problem would be appreciated.

joel0002 · Answer

With the saml authentication in the Username Attribute you can enter the path where the Appian username is located in the SAML assertion. So for example I use the email address which matches the users appian username. It would depend very much on what is available in your SAML assertion to what you can do here. One slightly annoying thing is that the casing in Appian cannot be changed you can only change the casing in the SAML assertion. So for example if you have JoeBloggs as the username in Appian but the username in the SAML assertion is joebloggs then you probably need to rename the user in Appian. However this is where I would start.

Mathieu Drouin · Answer

Did you try the " Use Lowercase" option? 
 Otherwise, I would opt for 's solution.