Bug 1261944 - (targetattr = "*") is mandatory to include in ACI while setting an ACI. But guide have wrong statement.
Summary: (targetattr = "*") is mandatory to include in ACI while setting an ACI. But g...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-deployment-guide
Version: 10.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Marc Muehlfeld
QA Contact: Viktor Ashirov
URL:
Whiteboard:
: 1371559 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-10 13:28 UTC by Amita Sharma
Modified: 2016-12-16 10:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-16 10:40:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Amita Sharma 2015-09-10 13:28:39 UTC
Description of problem:
(targetattr = "*") is mandatory to include in ACI while setting an ACI. But guide have wrong statement.

Version-Release number of selected component (if applicable):
RHDS10

https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/9.0/pdf/Deployment_Guide/Red_Hat_Directory_Server-9.0-Deployment_Guide-en-US.pdf

Existing Text :: Section 9.7.1.1 Targets :: 
Says "Further, the default set of attributes targeted by the ACI is any attribute available in the targeted entry's object class structure."

Which mislead to the conclusion that if you don't specify (targetattr = "*") in ACI, then it takes the default value as (targetattr = "*").

BUT, that is not true, you have to specify (targetattr = "*") otherwise things don't work properly.

For more details and example, please check::
https://bugzilla.redhat.com/show_bug.cgi?id=1210852

Comment 2 Marc Muehlfeld 2016-11-18 14:27:21 UTC
*** Bug 1371559 has been marked as a duplicate of this bug. ***

Comment 4 Amita Sharma 2016-11-28 08:22:53 UTC
Thanks William and Marc, sorry for delaying in the response.

Comment 5 Marc Muehlfeld 2016-12-16 10:40:13 UTC
The update is now available on the Customer Portal.


Note You need to log in before you can comment on or make changes to this bug.