Red Hat Bugzilla – Bug 97675
LDAP TLS Encryption Fails
Last modified: 2015-01-07 19:05:32 EST
Description of problem: LDAP does not work when TLS encryption is used on LDAP clients. Version-Release number of selected component (if applicable): 2.0.27-8 How reproducible: Always Steps to Reproduce: 1. Configure a Red Hat Linux 9.0 LDAP server: https://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-ldap-quickstart.html 2. Configure a Red Hat Linux 9.0 LDAP client with TLS encryption disabled: https://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-ldap-pam.html 3. If no user accounts were added to the LDAP database with the migration tools, then added a test user account. 4. Create a local home directory for the LDAP user on the LDAP client host. 5. Confirm there is no local account for the LDAP user on the LDAP client host. 6. Log in without GDM (su, ssh, a tty login screen, etc) to confirm it works. 7. Enable TLS encryption on the LDAP client host. 8. Log in without GDM (su, ssh, a tty login screen, etc) to verify failure. Actual results: Error message below is printed by ldap client or in /var/log/messages file. ldap_starttls_s: Connect error Expected results: TLS encryption to work with LDAP clients. Additional info: An excerpt from the /var/log/messages file on the LDAP client system is attached. The several lines show LDAP TLS start failure messages. Then they are followed by successful testuser0 log in sessions from the login (tty1), su, and sshd utilities.
Created attachment 92478 [details] /var/log/messages
Do not use GDM to log in to the LDAP client host because it does not work. I reported this in the 97676 ticket.
Hello, I resolved the problem. I followed the resolution provided by Nalin Dahyabhai in the 51352 ticket. I had to regenerate the /usr/share/ssl/certs/slapd.pem file with the LDAP server host name that the LDAP client was configured to use. I did that earlier, but forgot to change the group and permissions so the ldapd user could read the file. Sorry, for submitting this ticket. I did not read and follow the resolution in the 51352 ticket carefully. This information should be documented. May be I over looked it. I did not see this in the Red Hat Reference Guide or DAP Linux HOWTO. *** This bug has been marked as a duplicate of 51352 ***