ISE : Active Directory integration long usernames sAMAccountname

[tbostrom]

Have a customer deploying ISE for wireless authentication using PEAP-MSCHAPv2.  They've encountered an issue where some users with long usernames are failing authentication to ISE.  ISE logs that the user is not found in the user database (Active Directory).

Upon further review, it appears that ISE is using the sAMAccountname as the username token to authenticate against.

sAMAccountname is limited to 20 characters. 

Customer is running a full Windows 2008 domain and users login to the domain using their User Principal Name (no 20 character limit).  Therefore, when the user creates a wireless connection and passes his Windows credentials to PEAP, it fails because the username is too long and ISE does not find user in AD database.

Is there a way to point ISE to use a different username token instead of sAMAccountname?  or is this a known issue?

[Ravi Singh]

I don't think there is any way to increase the limit of 20 characters. You have to create to user name with 20 characters limit.

[tom.barat@dimensiondata.com]

I ave the same issue with one of my clients.

Any chance this has been fixed in the last 7 years or someone found a workaround ?

[victor.jaouen]

Any update on this limitation ?

[hslai]

See 

• CSCvf21978 ISE failing to resolve ambiguity for AD accounts
• CSCvc86398 ISE 2.1 patch 2 some certificate authentications fail

[tom.barat@dimensiondata.com]

Thank you for sharing these bugs.

They don't match exactly our issue (bugs mention issues for short usernames, we have issues with long ones) but it might help the TAC find the issue faster.

Have a nice day.

[andy!doesnt!like!uucp]

Hi Tom

do u have any conclusions on the case with TAC? i'd highly appreciate.

[tom.barat@dimensiondata.com]

Hello,

No, i wanted to collect logs before opening the TAC case but the users running into this issue are on vacation currently.

I'll be sure to update once this is solved in our environment.

Have a nice day,

Best regards.