I'm trying to configure a LDAP server with some basic security parameters, including TLS and required authenticated binding.
I have started the server, and can access it from localhost with the command:
ldapsearch -x -b 'dc=server,dc=com' 'objectclass=*' -W -D 'cn=manager,dc=server,dc=com' -H ldaps://server.com:389
When I try the same command remotely, from my computer, I get the following err
Dear All,
can anyone tell me what is the difference between these two files of LDAP client /etc/ldap.conf and /etc/ldap/ldap.conf and for what purposes these two files gives services. Is it necessary to have these two files at a time ?
I have a windows ldap client setup and I have been able to connect to it using the gui ldap admin client. When I try to connect to it using my ubuntu 12.04 client I get the following error in my auth.log:
Aug 21 16:38:20 uby getent: nss_ldap: failed to bind to LDAP server
ldap://pdc.ad.company.com:389: Invalid credentials
I have a Debian 6.0.5 server running openldap. It appears to be compiled against gnutls.
I followed the guide from the below link to set up a ldap server. After everything is finished, I configured a client for ldap authentication and I can search the entries in ldap using the command
ldapsearch -x ZZ but when I am trying to login to the client using a ldap user, the prompt just keeps waiting.
Hi,
I've been trying to find the answer with no luck. I'm hoping someone can help me. Here's what I need to do:
Run a KSH script that will check:
1. Server (Client) Type (AIX 5.3, 6.1, SUSE, and HP-UX are the possibilities).
2. LDAP.cfg is configured correctly and the ldap client service is running.
What I've Done:
I've successfully installed and configured Subversion Edge 3.1.2 with LDAP support on a Windows 2008 server. I have configured LDAP users and am able to use LDAP credentials to work on repositories just fine. No issues whatsoever.
* CentOS 5.8, LDAP server & client* Multiple CentOS 5.8 and CentOS 6.3 LDAP clientsSymptom: Client authentication requests for some users succeed while other users fail.
I am currently trying to add LDAP support to supplement a file auth system. Unfortunately, I can't just phase out the file system in it's entirety because of when the LDAP server goes down. The current status is that I have a system that works for both LDAP and file login, if the LDAP server is online and responding. But, when the LDAP server goes down, that is when I encounter issues.