Bug 44620 – self-sevice join scripts run in wrong order

Bug 44620 - self-sevice join scripts run in wrong order


Summary:	self-sevice join scripts run in wrong order

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Self Service
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-05-17 11:37 CEST by Daniel Tröder
Modified:	2020-07-03 20:55 CEST (History)
CC List:	0 users

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?:	4: A User would return the product
User Pain:	0.069
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
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 Daniel Tröder

2017-05-17 11:37:34 CEST

Because univention-self-service-passwordreset-umc was added as a dependency for univention-self-service, the join script
35univention-self-service-passwordreset-umc.inst runs before
34univention-self-service.inst

That leads to the UMC policy cn=selfservice-umc-servers not yet existing, when allow=cn=passwordreset-all should be added to it. Which surprisingly doesn't lead to an error when using the reset module... at least not if installed on the dc master.

Either the UMC policy cn=selfservice-umc-servers must (also) be created in 35univention-self-service-passwordreset-umc.inst, the execution order changed or the UMC policy is not needed.

Comment 1 Ingo Steuwer

2020-07-03 20:55:39 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.