Bug 49648 – TLS certificate of slapd can't be changed even with trusted CA

Bug 49648 - TLS certificate of slapd can't be changed even with trusted CA


Summary:	TLS certificate of slapd can't be changed even with trusted CA

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-06-13 17:23 CEST by Valentin Heidelberger
Modified:	2022-12-08 17:52 CET (History)
CC List:	3 users (show)

See Also:	30558
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Valentin Heidelberger

2019-06-13 17:23:01 CEST

Changing the TLSCertificate{File,KeyFile} and TLSCACertificateFile to custom settings results in a broken UMC login. It complains about a self-signed certificate, even if the CA was imported to the ca store and is considered trusted.

The customer has their own CA with which the sign pretty much anything in their environment. Since they want to access the LDAP from outside UCS servers as well they would've like to be able to use their CA.

The relevant config is in: /etc/univention/templates/files/etc/ldap/slapd.conf.d/30univention-ldap-server_head

Workaround: Import UCS Root CA on such non-UCS systems. It can be obtained from the master:

master.ucs.local/ucs-root-ca.crt

Comment 1 Ingo Steuwer

2019-06-13 17:40:12 CEST

The issue here is that the UCS root certificate and the host certificate must be part of the same CA.

Workarounds:

* the UCS root CA can be signed by an other CA. Afterwards all server certificates are trusted both by UCS instances and by other instances trusting the other CA.

* the host certificates and the public UCS root certificate can be replaced by the existing CA.

I keep this Bug open to review if the current check of OpenLDAP certificate with the UCS root CA is usefull.