New answers tagged

0

Shared libraries don't typically produce their own debug output by default - the programs that link them are supposed to take care of that, because they may use various ways to communicate to the user: the console, some sort of X output, syslog, ... Did you try calling ldap_set_option(..., LDAP_OPT_DEBUG_LEVEL, LDAP_DEBUG_TRACE) from the program you link to ...


1

In most cases, you don't need to have a bind password on the client at all. Instead, the system tries to bind with the username and password the user supplied and if that suceeds, will log you in. On my systems, I use a bind password only for administration tasks on the LDAP server. Other than that: If you have 80 clients, you really should already have ...


1

this works for me using sssd-ldap against a freeipa ldap server (not using the built-in idm provider but the sssd-ldap provider as asked). install sssd-ldap and authoconfig run authconfig --enablesssd --enablesssdauth --enablelocauthorize --update create the configuration file /etc/sssd/sssd.conf with your appropriate information: [domain/default] ...


0

I was following the same guide and had the same issue. It will work if you do the steps to "Tighten up ownership and permissions" listed after the offending ldapmodify command first--namely: sudo adduser openldap ssl-cert sudo chgrp ssl-cert /etc/ssl/private/ldap01_slapd_key.pem sudo chmod g+r /etc/ssl/private/ldap01_slapd_key.pem and sudo systemctl ...


0

It depends. This is a fairly poor format for such a question, and we have no idea on the aspects of your environment that guide such decisions. To cram an answer in before it's closed, consider tools native to rh/centos, such as: Freeipa/idm for auth/dns Spacewalk/satellite for patch management & deployment I'm fairly sure this question will be ...


0

I changed my domain name to provide.example.com and made sure I do the certification right and ldaps worked just fine on the server and added a new user and retrieved through ldapsearch. Then I setup the client and ran: ldapwhoami -H ldaps://provider.example.com -x -D "cn=Manager,dc=example,dc=com" -W and did get: dn:cn=Manager,dc=example,dc=com and will ...


0

Just adding your own sollution as an answer for readability: The problem was that I was using a different server name when creating a certificate and now it did not want to accept the certificate. So, when I correct the line: AuthLDAPUrl "ldap://ldap.domen.lan/dc=domen,dc=lan" TLS with server name in certificate, it worked!


1

Have you tried ldap:/// ldaps:///? Per this page http://www.openldap.org/doc/admin24/runningslapd.html, ldapi is ldap over ipc.


0

So it seems that the "--with-berkley-db" tag is not valid anymore. If you try this at home, use brew reinstall openldap --with-berkeley-db4 I just hope that I'll get my old data to work again...



Top 50 recent answers are included