Created by: James Maudlin on 20-05-2011 10:22:17 AM <h2> WebEx Social LDAP 101</h2> <h2> </h2> <h2> Using "ldapsearch" to verify LDAP binding, search results, and performance</h2>
While WebEx Social has built in tools to help you verify that your Principal Account can bind to LDAP and give you examples of LDAP mappings, how do you handle an issue where you can't successfully bind to LDAP, the results come back slowly, or you see results that are unexpected?
Luckily, there is a tool on the WebEx Social nodes that allows you to run an LDAP query and see the results in the command line. It is called "ldapsearch" and here is some sample syntax: <pre>ldapsearch -x -h <LDAP_Server_Host/IP> -p 389 -D "CN=<your_admin_account>,OU=<your_OU>,DC=<domain>,DC=<com,org,net,local,etc>" -W -b "<what you want to search for - e.g.: CN=chrchand,OU=Employees,OU=Cisco Users,DC=cisco,DC=com" </pre>
where: <ul> <li> LDAP_Server_Host/IP = the hostname or IP address of the LDAP Server (Active Directory Domain Controller, for example)</li> <li> -p 389 = Connecting on TCP port 389 (the default, but you might need to change for certain customers)</li> <li> -D = Designates that what follows is the Common Name (CN) for the account you want to use to authenticate (AKA: bind) with LDAP</li> <li> -W = Will prompt you to enter the password for the account used in the -D flag above</li> <li> -b = Designates that what follows is the search base of what you are searching for. Typically, this would be the CN of a particular user account, but you could search an entire OU. Just keep in mind this would return many results in a production environment.</li> </ul>
Here is an example of the command and its output. The command itself has been colored blue, the resulting LDAP query colored in red, and the rest of the output in green in order to make them easier to see: XXXXX in thread = userid
As we can see from the output, we get alot of information about the user in question, This helps us validate that we can successfully bind and search for the user, but it also gives us a chance to see each of the LDAP attributes for the user so we can troubleshoot any oddities that might result (e.g.: missing phone number, first and last name mis-mapped, etc). <h3> What to do when things go wrong</h3>
OK, so we know what things look like when it works. But what do you do when you get an error like this instead of all that output above: <pre>ldap_bind: Invalid credentials (49) additional info: 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece </pre>
How do we translate this into plain English? While not the definititive link for everything related to potential LDAP errors, this link has very good information on not only what a particular error code means, but what you might do to resolve it.
Subject: RE: Troubleshooting LDAP Replied by: duncan westlake on 22-09-2011 09:01:17 AM Hi James,
I have been using "ldapsearch" on WebEx Social 2.1 to test some import issues successfully. WebEx Social 2.5 SR1 does not seem to have the "ldapsearch" function any more. Has it been removed or is it used / called in a different way?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: