We have SSO logins but need to bypass some users with too long UPN/email

[Sue L]

We have been using SSO for some time now and always had 7-character userids , but when we went to Entra (from AD)  security moved us to UPN, which in reality is the email address of the person now for our User field.  In the first couple months were were using email in the user field on the Advanced tab, however it was a struggle with hyphenated names , where it seemed to be a mix of whether the hyphen was in the UPN or not (whatever HR was choosing?) Anyway, I changed the User Field to user_name and that fixed that issue.  OK, we have 2 users that exceeded the 40 character user limit (unbeknowst limitation til we moved to email address!) they still need to use their 7-char userid and then go through MFA instead of SSO. However the login.do page still denies them. I have even tried changing the user to a local login password. 

Any advice?  As I see Adaptive authentication, but seems to be more IP based/domain... basically I just want to allow these 2 users and everyone else stay with SSO....    

[Sue L]

and yes, while I want security to change their emails, apparently it is a LONG process.... not happening soon.

[Tanushree Maiti]

Hi @Sue L 

We encountered a similar issue with one of our clients where the domain name after the @ symbol in the email address was quite long. As a result, email addresses for users with longer usernames were being truncated because the out-of-the-box (OOB) email field had a limited character length. This truncation caused SSO authentication to fail.

To resolve the issue, we customized the email field by increasing its maximum character length to 80 (approximately, as this was implemented about two years ago). After increasing the field length, the SSO login worked as expected.