Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

using LDAP with eDir

I've been trying to configure serv-u v15 with ldap hosted on an eDir system.

the DN i've been told to use is "ou=corp,ou=users,o=rs_corp" and a filter like "(cn=$LoginID)"

I'm able to use ldapsearch to verify the connection to the ldap server, and the data, but i have not been able to get serv-u to grant me a login for an account.

I have "Use LDAP group home" checked, and the group template home path set to a valid directory structure on the server.

Are there any logs to show what ldap is doing why it fails? I haven't found such.

Any pointers or tips?

Find more posts tagged with

ldap

edir

serv-u

Accepted answers

All comments

dougpapenthien

We have some improvements coming to LDAP authentication, including better support for more LDAP servers and improved logging to help diagnose and troubleshoot LDAP login issues.

In the meantime, here are some things to check:

Usually, the base DN value is something like "DN=solarwinds,DN=com". Your search filter should still restrict the objectclass to User. By using "cn=$LoginID", you're also stating that the attribute in eDir that represents the login ID provided by the user is named "cn". I would double-check that this is true. You could use something like ldapsearch to run a query against the server to verify the search filter string.
A current limitation of Serv-U's LDAP support is that the credentials supplied by the user during login must be valid credentials to perform bind operations on the LDAP server. This is always true when using LDAP on top of an AD server, but may not be true for other LDAP servers. This is one of the big limitations we're looking to address in the upcoming LDAP improvements by adding the ability to specify account credentials for the bind operations in your LDAP server configuration. This may be your root issue, but I don't know enough about eDir to say for sure.
While trying to verify LDAP settings, just setup a home directory (don't forget to add the directory access rule for %HOME%) within the "Default LDAP Group". Once you've verified this, then try setting up your LDAP group structure.
When setting up your LDAP group structure, be sure to include the full base DN in your setup. For your example, the LDAP group hierarchy in Serv-U would look like: rs_corp -> users -> corp -> etc