09-15-2014 08:08 AM - edited 03-17-2019 04:28 PM
Just wondering if there is a way to make the sign in to Jabber a little more seamless in the situation where a persons email address is not in the same format as their AD username.
Example : bob.dole@domain.com when his username is doleb
If anyone has any ideas on how to solve this, I'd love to hear it.
09-17-2014 10:29 AM
I have the same problem, and still trying to work around it.
What are you using for the IMP login value? (IMP Address Scheme)
I have mine set to Directory URI with the indent that users could use their email address as their login and running into multiple issues with that deployment.
09-18-2014 08:39 AM
I'm running version 9. not sure that the IMP address scheme setting can be change until version 10.
It would appear that my only options are changing the field used for the user ID during the LDAP import in CUCM. None of which work well. The best of the bunch is the default samaccountname which is what is causing this issue.
Spoke with TAC and I've been told I am SOL and it will just have to be a matter of user education to use userid@domain instead of their actual email address.
09-19-2014 02:43 PM
Justin
I never did solve this, however, I just began testing Jabber for Windows 10.5 and it no longer requires a "email" to sign in. You seem to be able to use just the username.
However, it didn't like the domain\username format, so if you have mutiple domains, I'm not sure if it will work with username only. In these cases you might need username@domain.
-Mark
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide