Univention Bugzilla – Bug 33354
policy result displayed incorrectly when "empty attributes" is set
Last modified: 2017-08-08 07:11:38 CEST
Created attachment 5621 [details] policy.ldif empty attributes are displayed, fixed attributes are maybe also broken.
Created attachment 5622 [details] screenshot
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.
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).
Fixed by Bug #38712 ?
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.
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.