Bug 1467516 - Add example to ACI Placement
Add example to ACI Placement
Status: NEW
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-administration-guide (Show other bugs)
10.1
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Marc Muehlfeld
Viktor Ashirov
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-04 02:12 EDT by Marc Muehlfeld
Modified: 2017-07-04 02:12 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marc Muehlfeld 2017-07-04 02:12:52 EDT
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/managing_access_control#Access_Control_Principles-ACI_Placement



Section Number and Name: 
14.1.2. ACI Placement
> If an entry containing an ACI does not have any child entries, the ACI
> applies to that entry only. If the entry has child entries, the ACI
> applies to the entry itself and all entries below it. As a direct
> consequence, when the server evaluates access permissions to any given
> entry, it verifies the ACIs for every entry between the one requested
> and the directory suffix, as well as the ACIs on the entry itself. 



Suggestions for improvement: 
Add an example.

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