RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 786629 - [ipa webui] permission with filter or subtree does not allow attr to be specified
Summary: [ipa webui] permission with filter or subtree does not allow attr to be speci...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Martin Prpič
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On: 783536
Blocks: 819997
TreeView+ depends on / blocked
 
Reported: 2012-02-01 23:48 UTC by Dmitri Pal
Modified: 2012-05-10 17:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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.
Clone Of: 783536
: 819997 (view as bug list)
Environment:
Last Closed: 2012-05-10 17:10:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 3 Rob Crittenden 2012-04-02 15:45:12 UTC
    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.

Comment 4 Martin Prpič 2012-04-15 12:57:40 UTC
    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.


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