Bug 33354 - policy result displayed incorrectly when "empty attributes" is set
policy result displayed incorrectly when "empty attributes" is set
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Policies
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 3.2-x
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-13 14:22 CET by Florian Best
Modified: 2017-08-08 07:11 CEST (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
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
policy.ldif (3.48 KB, text/x-ldif)
2013-11-13 14:22 CET, Florian Best
Details
screenshot (34.17 KB, image/png)
2013-11-13 14:23 CET, Florian Best
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2013-11-13 14:22:40 CET
Created attachment 5621 [details]
policy.ldif

empty attributes are displayed, fixed attributes are maybe also broken.
Comment 1 Florian Best univentionstaff 2013-11-13 14:23:05 CET
Created attachment 5622 [details]
screenshot
Comment 2 Philipp Hahn univentionstaff 2014-07-09 08:20:24 CEST
While working on Bug #33351 I noticed that the "required/excluded object class" handling looks also broken: I used the object-class "univentionDomainController" for my quick test using a UCR policy: putting the OC in prohibited the policy was first not applied (which matches my expected result), but after moving to to required and back to prohibited the policy was the still applied.
Comment 3 Dmitry Galkin univentionstaff 2014-08-05 15:10:41 CEST
Fixed and empty were working correctly recently (tested by Bug #35314 for non-UCR policies), but required/excluded object classes were not inherited in the UMC (Bug #35423).
Comment 4 Florian Best univentionstaff 2015-06-30 13:31:33 CEST
Fixed by Bug #38712 ?
Comment 5 Stefan Gohmann univentionstaff 2017-06-16 20:37:09 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 6 Stefan Gohmann univentionstaff 2017-08-08 07:11:38 CEST
This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly 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 this issue. In this case please provide detailed information on how this issue is affecting you.