Bug 57014 – Initialization from Backup Directory Node did not work

Bug 57014 - Initialization from Backup Directory Node did not work


Summary:	Initialization from Backup Directory Node did not work

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	AD Connector
Version:	UCS 5.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2024-01-31 12:27 CET by Robert Heyer
Modified:	2024-01-31 12:28 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
screenshot (18.30 KB, image/png) 2024-01-31 12:27 CET, Robert Heyer	Details
View All 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 Robert Heyer

2024-01-31 12:27:37 CET

Created attachment 11180 [details]
screenshot

Installing the AD-Connector on a Backup Directory Node (variant two, sync mode) and use the non encryption connection option to the Active Directory, leads to the following message: 

"Erstellung eines neuen Zertifikats fehlgeschlagen (/etc/univention/ssl/$FQDN). The same procedure on a primary directory node works.