Bug 39484

Summary:	univention.s4connector.s4.explode_unicode_dn looses the last RDN element
Product:	UCS	Reporter:	Arvid Requate <requate>
Component:	S4 Connector	Assignee:	Samba maintainers <samba-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P5	CC:	best, birkefeld, botner, gohmann, grandjean, oyen, petersen, requate
Version:	UCS 4.4
Target Milestone:	---
Hardware:	Other
OS:	Linux
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=32086
What kind of report is it?:	Development Internal	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?:
School Customer affected?:		ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):	Cleanup, Troubleshooting
Max CVSS v3 score:

Description Arvid Requate

2015-10-06 22:07:36 CEST

univention.s4connector.s4.explode_unicode_dn looses the last RDN:


>>> import univention.s4connector.s4
>>> univention.s4connector.s4.explode_unicode_dn('DC=abc,DC=def')
['DC=abc']

This is as old as univention-ad-connector and we should check what other implications it might have before fixing it.


+++ This bug was initially created as a clone of Bug 34184#c17 +++

Comment 1 Lukas Oyen

2017-09-18 14:07:24 CEST

The code in question still exists, but is no longer used with the DN escaping from bug #32086. Only the (unused) `old_user_dn_mapping()` function ever calls `explode_unicode_dn()`.

In fact `explode_unicode_dn()` and `old_user_dn_mapping()` are dead code to be removed with the patch attached to bug #43068.

Comment 2 Stefan Gohmann

2019-01-03 07:19:05 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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

Comment 3 Florian Best

2019-08-08 16:43:16 CEST

Removed in Bug #43068.

*** This bug has been marked as a duplicate of bug 43068 ***