Bug 50086 – Can't sync renamed Object when uid<>samAccountName is changed

Bug 50086 - Can't sync renamed Object when uid<>samAccountName is changed


Summary:	Can't sync renamed Object when uid<>samAccountName is changed

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.4
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:	2019-08-29 14:29 CEST by Nico Stöckigt
Modified:	2019-08-29 14:35 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	4: A User would return the product
User Pain:	0.183
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2019082821000761
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 Nico Stöckigt

2019-08-29 14:29:48 CEST

When changing the Users name along with the Username (uid <> samAccountName) the S4-Connector seems not to be able to find the related object resulting in a reject or even two independent objects.

The Connector should be able to track tis down, probably by using objectSID <> sambaSID to find the corresponding object.