Bug 97675 - LDAP TLS Encryption Fails
Summary: LDAP TLS Encryption Fails
Status: CLOSED DUPLICATE of bug 51352
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: openldap   
(Show other bugs)
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Jay Turner
Depends On: 51352 97676
TreeView+ depends on / blocked
Reported: 2003-06-19 04:39 UTC by Gabriel Donnell
Modified: 2015-01-08 00:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-19 08:25:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/messages (5.23 KB, text/plain)
2003-06-19 04:42 UTC, Gabriel Donnell
no flags Details

Description Gabriel Donnell 2003-06-19 04:39:42 UTC
Description of problem:
LDAP does not work when TLS encryption is used on LDAP clients.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configure a Red Hat Linux 9.0 LDAP server:
2. Configure a Red Hat Linux 9.0 LDAP client with TLS encryption disabled:
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

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

Comment 1 Gabriel Donnell 2003-06-19 04:42:25 UTC
Created attachment 92478 [details]

Comment 2 Gabriel Donnell 2003-06-19 04:53:01 UTC
Do not use GDM to log in to the LDAP client host because it does not work.
I reported this in the 97676 ticket.

Comment 3 Gabriel Donnell 2003-06-19 08:23:59 UTC

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 ***

Note You need to log in before you can comment on or make changes to this bug.