Because a permission does not provide write access to an entry, delegation does not work as expected. The 389 Directory Server (389-ds) distinguishes access between entries and attributes. For example, an entry can be granted add or delete access, whereas an attribute can be granted read, search, and write access. To grant write access to an entry, the list of writable attributes needs to be provided. The filter, subtree, and other options are used to target those entries which are writable. Attributes define which part(s) of those entries are writable. As a result, the list of attributes will be writable to members of the permission.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: A permission doesn't provide write access to an entry
Consequence: Delegation does not work as expected
Fix: 389-ds distinguishes access between entries and attributes. One grants add or delete access to an entry but read, search and write access to an attribute. To grant write access on an entry the list of writable attributes needs to be provided. The filter, subtree, etc. are used to target those entries which are writable. Attributes define which part(s) of those entries are writable.
Result: The list of attributes will be writable to members of the permission.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,7 +1 @@
-Cause: A permission doesn't provide write access to an entry
+Because a permission does not provide write access to an entry, delegation does not work as expected. The 389 Directory Server (389-ds) distinguishes access between entries and attributes. For example, an entry can be granted add or delete access, whereas an attribute can be granted read, search, and write access. To grant write access to an entry, the list of writable attributes needs to be provided. The filter, subtree, and other options are used to target those entries which are writable. Attributes define which part(s) of those entries are writable. As a result, the list of attributes will be writable to members of the permission.-
-Consequence: Delegation does not work as expected
-
-Fix: 389-ds distinguishes access between entries and attributes. One grants add or delete access to an entry but read, search and write access to an attribute. To grant write access on an entry the list of writable attributes needs to be provided. The filter, subtree, etc. are used to target those entries which are writable. Attributes define which part(s) of those entries are writable.
-
-Result: The list of attributes will be writable to members of the permission.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: A permission doesn't provide write access to an entry Consequence: Delegation does not work as expected Fix: 389-ds distinguishes access between entries and attributes. One grants add or delete access to an entry but read, search and write access to an attribute. To grant write access on an entry the list of writable attributes needs to be provided. The filter, subtree, etc. are used to target those entries which are writable. Attributes define which part(s) of those entries are writable. Result: The list of attributes will be writable to members of the permission.