Bug 47376 – UCS-System objects can't be moved to an alternative position without effecting the products behavior

Bug 47376 - UCS-System objects can't be moved to an alternative position without effecting the products behavior


Summary:	UCS-System objects can't be moved to an alternative position without effectin...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 4.3
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-07-18 18:04 CEST by Nico Stöckigt
Modified:	2021-05-14 16:34 CEST (History)
CC List:	3 users (show)

See Also:	48984
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?:	5: Blocking further progress on the daily work
User Pain:	0.229
Enterprise Customer affected?:	Yes
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018071621000608, 2018081521001751
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

2018-07-18 18:04:29 CEST

Several functions seem to expect an UCS system object to be at it's designated position 'cn=dc|memberserver,cn=computers,dc=ldap,dc=base' due to hardcoded ldap ACLs (66univention-appcenter_app.acl).

There might be situations when it's needed to freely move such an object to another position, e.g. when there is a policy assigned to the default container which shouldn't apply to that system.

We should either make the ACL more flexible or persistently configurable.

Comment 1 Arvid Requate

2019-03-14 15:55:46 CET

We need more specific examples to make changes here.

Comment 2 Ingo Steuwer

2021-05-14 15:42:40 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 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.