Bug 42522 – Change post con modify function order

Bug 42522 - Change post con modify function order


Summary:	Change post con modify function order

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-09-28 06:00 CEST by Stefan Gohmann
Modified:	2019-01-03 07:19 CET (History)
CC List:	1 user (show)

See Also:	41302 42523
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.034
Enterprise Customer affected?:	Yes
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016090921000131
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 Stefan Gohmann

2016-09-28 06:00:21 CEST

In Ticket #2016090921000131, the users were disabled after they have been created. This happened due to a problem in the primary_group_sync post con modify function. Since the user activation in AD is the last post con modify step, the user were synced back disabled.

We should change the order and do the user activation before changing the group settings.

Comment 1 Stefan Gohmann

2019-01-03 07:19:21 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.