Bug 159151

Summary: Authconfig update creates a problem with OpenLDAP server
Product: Red Hat Enterprise Linux 4 Reporter: Tomas Mraz <tmraz>
Component: openldapAssignee: Jay Fenlason <fenlason>
Status: CLOSED ERRATA QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: jfeeney, srevivo, tao
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: RHSA-2005-767 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-17 07:50:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tomas Mraz 2005-05-30 18:33:52 UTC
Description of problem:
Authconfig update in RHEL4 U1 always adds if the authconfig is run a
TLS_CACERTDIR directive to the /etc/openldap/ldap.conf with value
/etc/openldap/cacerts. However this directory is created only if user selects a
TLS option on the LDAP config dialog. The OpenLDAP server fails to start if the
directive is in the ldap.conf file and the directory doesn't exist.

Additional info:
This should be fixed either by openldap creating and owning this directory or by
authconfig - ensuring that it doesn't write the directive to the ldap.conf if
TLS is not on. However I think that the directory should be owned by some
package anyway so the former solution is more correct (and easier as it doesn't
require any code change - only packaging).

Comment 2 Eric Paris 2005-07-05 16:19:50 UTC
Avaya would like to know how we plan to fix this.  Option one seems to be the
best idea.  Please advise.

Comment 8 Red Hat Bugzilla 2005-10-17 07:50:10 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.