Bug 34519 – univention-s4-position-sync computes wrong DN if DNS domain name doesn't match LDAP base

Bug 34519 - univention-s4-position-sync computes wrong DN if DNS domain name doesn't match LDAP base


Summary:	univention-s4-position-sync computes wrong DN if DNS domain name doesn't matc...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Samba4
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-04-09 17:15 CEST by Jan Christoph Ebersbach
Modified:	2020-07-03 20:52 CEST (History)
CC List:	2 users (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?:	5: Blocking further progress on the daily work
User Pain:	0.086
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2014040821001626
Bug group (optional):
Max CVSS v3 score:

Flags:	gohmann: Patch_Available+

Attachments
Fixes LDAP base replacement (642 bytes, patch) 2014-04-09 17:15 CEST, Jan Christoph Ebersbach	Details \| Diff
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 Jan Christoph Ebersbach

2014-04-09 17:15:44 CEST

Created attachment 5863 [details]
Fixes LDAP base replacement

Reported at Ticket #2014040821001626

On a UCS system with the LDAP dc=yy,dc=zz and the DNS domain name xx.yy.zz the S4 migration script univention-s4-position-sync computes the new position for UCS DCs as follows:  cn=ucsdc,ou=domain controllers,dc=xx,DC=XX,DC=YY,DC=ZZ

It duplicates the first LDAP base component (dc=xx) and computes a wrong position.

The attached patch tries to solve the issue running the LDAP base replacement just once.  There might be untested corner cases.

Comment 1 Ingo Steuwer

2020-07-03 20:52:05 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.