What else could you need? I was able to setup the server and search domain very easily.
A LDAP server configuration can be different in every shape or form. Just because you were able to setup a LDAP client with very minimal information that work may not work for a company that setup a different way of how their LDAP server is configured. A majority of our customers use our LDAP client without having to change the "advanced" settings but there are others where we have to sometime help our customers to figure out how their LDAP server is configured and modify the "advanced" settings to be able to get the LDAP client to work properly.
The last issue that I had to fix was how a customer configured their OpenLDAP server, the LDAP client couldn't use the Base DN that it figured out because it doesn't actually exist on the server. So, I had to make the client prompt the user for the actual Base DN.
The other LDAP configuration can be:
User Filter (which user object you want to filter from the server)
Group Filter (which group object you want to filter from the server)
Search Attributes (which attributes you want to search on the server)
LDAP Attributes (what are the LDAP attributes that the administrator used to create the LDAP objects for First Name, Last Name, Display Name, E-mail address, street, city, state, etc, etc, etc)
Here's a example of how one of the LDAP server could be configured.
Code:
UserFilter: objectClass=person
GroupFilter: objectClass=distroList
SearchAttribute: display-name;mail;givenName;cn;sn
BaseDN:
LDAP Attributes:
FirstName: givenName
LastName: sn
DisplayName: cn
EmailAddress: mail
Street: streetaddress
PostOfficeBox: postOfficeBox
City: l
State: st
PostalCode: postalCode
Department: department
HomePhone: homePhone
CellPhone: mobile
OfficePhone: workPhone
PagerNumber: pager
FaxNumber: facsimiletelephonenumber
TelexNumber: telexNumber
Title: title
OfficeName: physcialDeliveryOfficeName
Description: description
Server: mailHost
Alias: mailAlias
DistinguishedName: dn