[cisco-voip] CUCM AD integration

Ryan Ratliff rratliff at cisco.com
Thu Apr 29 09:33:16 EDT 2010


Also, you have to completely remove any existing ldap system before you can change it.  From my testing existing end users will be retained, but their userids will change in the db.   Any existing users that do not have a value set in AD for whatever attribute you choose you can expect to be purged.

-Ryan

On Apr 29, 2010, at 9:27 AM, Joe Martini (joemar2) wrote:

> The supported method is to use the GUI go to System > LDAP > LDAP System.  There you will find "LDAP Attribute for User ID".  You have limited choices but the GUI contains the attributes TAC supports.
> 
> Joe
> 
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Erich Novak
> Sent: Thursday, April 29, 2010 8:18 AM
> To: Ed Leatherman; charl.crofton at gmail.com
> Cc: cisco-voip at puck-nether.net
> Subject: Re: [cisco-voip] CUCM AD integration
> 
> Hi,
> 
> it is possible, but not via GUI, you can change it in the Database.
> 
> You need an Active Directory field with the DN of the User (ie. IPPhone) and take care that it is unique in AD.
> 
> Next you log on to the CUCM CLI via ssh, ->
> 
> admin:run sql select * from ldapsystemconfig
> pkid                                 useridattributename tkldapserver syncenabled
> ==================================== =================== ============ ===========
> a1cdb5e3-aaf4-4db0-bfa9-b7c872622365 sAMAccountName      1            t
> 
> 
> you can update the useridattributename to anything you want via run sql update...
> 
> but take care, this also has impact on CUPS etc.
> 
> brgds
> Erich
> 
> -----Ursprüngliche Nachricht-----
> Von: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] Im Auftrag von Ed Leatherman
> Gesendet: Donnerstag, 29. April 2010 14:01
> An: charl.crofton at gmail.com
> Cc: cisco-voip at puck-nether.net
> Betreff: Re: [cisco-voip] CUCM AD integration
> 
> I don't think this is possible Charl. Extension Mobility uses the userID and PIN for login, I don't know of a way to change that.
> 
> On Thu, Apr 29, 2010 at 6:03 AM, Charl Crofton <charl.ccrofton at gmail.com> wrote:
>> HI,
>> 
>> Let me try and explain this correctly:
>> 
>> CUCM integrated with AD & using Extension Mobility
>> 
>> So userid will be something like: jsoap (must be username to keep it 
>> uniform across the enterprise) My Device Profile will be something 
>> like: 12345 (user jsoap's extension number) Device Profile is 
>> associated with user jsoap.
>> 
>> I want users to log into the phones with their extension number
>> (12345) instead of having to use their username (jsoap)
>> 
>> Is this possible and if so, how?
>> 
>> thnx
>> charl
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>> 
> 
> 
> 
> --
> Ed Leatherman
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip




More information about the cisco-voip mailing list