Bug 31413 – unable to override ucr policy with "empty attributes"

Bug 31413 - unable to override ucr policy with "empty attributes"


Summary:	unable to override ucr policy with "empty attributes"

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - Policies
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-05-22 13:33 CEST by Tim Petersen
Modified:	2020-07-03 20:55 CEST (History)
CC List:	3 users (show)

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?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.069
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2014050921008045
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 Tim Petersen

2013-05-22 13:33:07 CEST

Chapter 4.5.1 in the doc mentions that you can override policy attributes with "empty attributes" in order to define exceptions.

This does not work for ucr-policies. It seems that the wrong attribute is mapped here.

Example policy-result ("eins" sets variable foo=bar, "zwei" sets ucr-variables empty):
Policy: cn=eins,cn=policies,dc=tim,dc=amd64
Attribute: univentionRegistry;entry-hex-666f6f
Value: bar

Policy: cn=zwei,cn=policies,dc=tim,dc=amd64
Attribute: registry

Comment 1 Tim Petersen

2014-05-16 14:24:30 CEST

Requested again 2014050921008045

Comment 2 Florian Best

2017-06-28 14:52:58 CEST

There is a Customer ID set so I set the flag "Enterprise Customer affected".

Comment 3 Ingo Steuwer

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