Bug 1547922

Summary:	libldap tlsmc continue even after it fails to extract CA certificate
Product:	Red Hat Enterprise Linux 7	Reporter:	Patrik Kis <pkis>
Component:	openldap	Assignee:	Matus Honek <mhonek>
Status:	CLOSED ERRATA	QA Contact:	Patrik Kis <pkis>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.5	CC:	nkinder, pkis
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openldap-2.4.44-14.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1550110 1563080 (view as bug list)		Environment:
Last Closed:	2018-10-30 07:47:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1550132, 1563080

Description Patrik Kis 2018-02-22 09:58:43 UTC

Description of problem:
libldap tlsmc should fail completly and remove temporary files when it fails to extract CA certificate. When upgrading openldap from RHEL-7.3 to RHEL-7.5 the extraction fails due to not yet updated seninux-policy, but openldap acts as if correctly extracted the certificates.
This causes that slapd does not start after upgrade and admin  have to manually remove /tmp/openldap-tlsmc* directories.

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

openldap-2.4.44-13.el7
How reproducible:
always

Steps to Reproduce:
1. Install RHEL-7.3 and set up openldap server.
2. Make sure slapd requires client certificate verification (dmand)
3. Upgrade the system to RHEL-7.5
4. Check that ldapsearch with TLS is working

Actual results:
slapd does not responds to ldapsearch because it has not access to certificates.

Expected results:
All is working as before the upgrade.

Additional info:

Comment 8 errata-xmlrpc 2018-10-30 07:47:50 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3024