LDAP integration, userid is limited to 20 characters

[joeharb]

We have a user that their AD account is 22 characters in length, but shows up in CUCM with the last 2 characters stripped.  They are not able to login into Jabber.  Is there a service setting that limits the username length?

Thanks,

Joe

[Nithin Eluvathingal]

End user can have more than 20 Character, on my lab I created a users with more than 20 character. I don't have an option to try it with LDAP now. 

[Jaime Valencia]

That's not configurable, from what I recall I think it was 32 characters max, you can take a look at the data dictionary from your version to confirm that, not sure if they changed it at some point.

You can also open a TAC for assistance to confirm the maximum and if it remains at 32, why it's not working.

[joeharb · Accepted solution]

After some research, it appears to be a limit on the AD side as the sAMAccountName is limited to 20 characters for backward compatibility.  Checking the user's account it is the same in AD as it is in CUCM.  

Thanks,

Joe

[Roger Kallberg]

Now I’m a little confused. Did you not check this before you made the assumption that it must be a problem with the CM sync of LDAP information?