cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1084
Views
0
Helpful
6
Replies

LDAP Query question

danhoffmann2010
Level 1
Level 1

I have Personal Communicator installed with presence, unity and call manager servers and Windows AD.

I have noticed that when Personal Communicator queries LDAP, it logs as domain\administrator and not the normal user.

Is there a setting I can change to have that show as domain\user?

I see from http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_6/english/install_upgrade/deployment/guide/dgactivedirconfig.html#wp1113230 that I can modify some registry settings to turn off the LDAP queries, but I'm not sure what real-world functionality I will lose.

The regedits I found are:

HKEY_CURRENT_USER\Software\Policies\Cisco Systems, Inc.\Client Services Framework\AdminData

LDAP_DisableNumberLookups = false

LDAP_SearchByUsername = false

Any help will be appreciated.

Dan

2 Accepted Solutions

Accepted Solutions

Jonathan Schulenberg
Hall of Fame
Hall of Fame

CUPC used a statically configured user account configured on the CUP server under Application > CUPC/Jabber > LDAP Servers. You cannot disable LDAP entirely; the settings you show there only disable queries against alternate attributes such as mobile or homePhone.

If you want to use the user's own credentials for LDAP queries you need to upgrade to a client that supports Enhanced Directory Integration. The late CUPC 8 client supported this as well the current Jabber for Windows client. Note that in both cases EDI only works if the user is logged in on a domain-joined PC (i.e. has an active Kerberos session).

CUPC: http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_6/english/cupc/cupcactivedirconfig.html#wp1112227

Jabber:

http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_2/JABW_BK_C9731738_00_jabber-windows-install-config_chapter_0101.html#JABW_RF_DE063FFA_00

Please remember to rate helpful responses and identify helpful or correct answers.

View solution in original post

Users cannot. Administrators can through BAT jobs on the IM&P server.

Please remember to rate helpful responses and identify helpful or correct answers.

View solution in original post

6 Replies 6

Jonathan Schulenberg
Hall of Fame
Hall of Fame

CUPC used a statically configured user account configured on the CUP server under Application > CUPC/Jabber > LDAP Servers. You cannot disable LDAP entirely; the settings you show there only disable queries against alternate attributes such as mobile or homePhone.

If you want to use the user's own credentials for LDAP queries you need to upgrade to a client that supports Enhanced Directory Integration. The late CUPC 8 client supported this as well the current Jabber for Windows client. Note that in both cases EDI only works if the user is logged in on a domain-joined PC (i.e. has an active Kerberos session).

CUPC: http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_6/english/cupc/cupcactivedirconfig.html#wp1112227

Jabber:

http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_2/JABW_BK_C9731738_00_jabber-windows-install-config_chapter_0101.html#JABW_RF_DE063FFA_00

Please remember to rate helpful responses and identify helpful or correct answers.

Thanks!  I am testing the Jabber Windows client now.

Do you knwo if you can export/import user contacts from the CUPC client?

Users cannot. Administrators can through BAT jobs on the IM&P server.

Please remember to rate helpful responses and identify helpful or correct answers.

That should mean that all contacts are stored on the presence server then?

If so, then after logging in with Jabebr, shoudn't I see all my contact info that I had setup?

I do not see any of the personal (non-domain) contacts I had added under the CUPC 8.6 client.

Ah, I read your question to mean bulk addition of contacts (i.e. import from a file). It appears that you're referring to a feature called Pizza Guy; a contact that doesn't exist on the server but you have defined locally for click-to-dial purposes only. This is a feature that was lost when the CUPC code was scrapped and Jabber was written from scratch. At present, the client requires all contacts to have a valid XMPP ID. Cisco is going to re-add this feature but I can't speak to timelines as those are NDA-protected. Until they do your backup option would be to click-to-dial from an Outlook contact instead.

Please remember to rate helpful responses and identify helpful or correct answers.

yeah....we use GroupWise and click-to-dial doesn't work.