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 784315 - doc: ipa permission-add: if no targetattr is specified, the default is no access to any attribute
Summary: doc: ipa permission-add: if no targetattr is specified, the default is no acc...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Identity_Management_Guide
Version: 6.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 6.3
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-24 14:49 UTC by Namita Soman
Modified: 2012-06-21 23:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-21 23:15:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Namita Soman 2012-01-24 14:49:17 UTC
Description of problem:
Add a permission with a subtree as a target. This will allow all attributes in this subtree to be modified. But can run cli to add a perm, and specify attr as below:

ipa permission-add ManageHost --permissions="write" --subtree=cn=computers,cn=accounts,dc=testrelm,dc=com --memberof=groupone --attr=locality

and there is no message indicating that the attr specified here is redundant, or will be ignored, or should not be allowed.

Version-Release number of selected component (if applicable):
ipa-server-2.2.0-101.20120117T0229zgit5febffb.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Add a permission as above

  
Actual results:
Permission is added:
-----------------------------
Added permission "ManageHost"
-----------------------------
  Permission name: ManageHost
  Permissions: write
  Attributes: locality
  Member of group: groupone
  Subtree: ldap:///cn=computers,cn=accounts,dc=testrelm,dc=com


Expected results:
Since permission will allow all attributes to be modified, the attr=locality is ignored....or not allowed.

Additional info:

Comment 2 Rob Crittenden 2012-01-24 15:19:56 UTC
I need to double-check with the 389-ds team on the assumption that specifying no attributes means all attributes.

Comment 3 Dmitri Pal 2012-01-24 15:25:29 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/2304

Comment 4 Rich Megginson 2012-01-24 21:42:34 UTC
in an aci, if you do not specify a targetattr clause, the default is no access to any attribute:

junk.ldif:
dn: dc=example,dc=com
changetype: modify
replace: aci
aci: (target ="ldap:///dc=example,dc=com")(targetattr != "userpassword")(versio
 n 3.0;acl "Anonymous read-search access";allow (read, search, compare)(userdn
  = "ldap:///anyone");)
aci: (target="ldap:///dc=example,dc=com") (targetattr = "*")(version 3.0; acl 
 "allow all Admin group"; allow(all) groupdn = "ldap:///cn=Directory Administr
 ators,ou=Groups,dc=example,dc=com";)

ldapmodify -f junk.ldif
ldapsearch -xLLL -h localhost -p 1200  -b dc=example,dc=com uid=scarter
dn: uid=scarter,ou=People,dc=example,dc=com
cn: Sam Carter
sn: Carter
givenName: Sam
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
ou: Accounting
ou: People
l: Sunnyvale
uid: scarter
mail: scarter
telephoneNumber: +1 408 555 4798
facsimileTelephoneNumber: +1 408 555 9751
roomNumber: 4612
manager: cn=uid=dmiller,ou=People,dc=example,dc=com

# every attribute except userpassword

but if I change the aci
dn: dc=example,dc=com
changetype: modify
replace: aci
aci: (target ="ldap:///dc=example,dc=com")(versio
 n 3.0;acl "Anonymous read-search access";allow (read, search, compare)(userdn
  = "ldap:///anyone");)
aci: (target="ldap:///dc=example,dc=com") (targetattr = "*")(version 3.0; acl 
 "allow all Admin group"; allow(all) groupdn = "ldap:///cn=Directory Administr
 ators,ou=Groups,dc=example,dc=com";)

ldapmodify -f junk.ldif
ldapsearch -xLLL -h localhost -p 1200  -b dc=example,dc=com uid=scarter
# nothing is returned

so in an aci, if you do not specify a targetattr, no attribute is allowed, and nothing is returned

Comment 5 Namita Soman 2012-01-25 14:41:05 UTC
In Doc:
15.4.2.1. Creating New Permissions from the Web UI
Step 6 indicates that 
<snip>
All attributes within the matching entries can be modified. 
<snip>

which is misleading. Based on Rich's explanation above, if no attributes are specified, then the default is no access to any attribute.

Comment 9 Deon Ballard 2012-05-03 16:33:44 UTC
Setting all priority and severity to medium.

Comment 12 Deon Ballard 2012-06-21 23:15:59 UTC
Closing.


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