Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
I don't know if this has been on purpose as a feature or if it could be considered as a bug. Customers are confused about this.
For them, adding a user to the group "cn=admins" is enough to make a user have the same rights of "admin" user.
But there's at least a Permission missing, that is to be able to do this:
aci: (targetattr = "krblastpwdchange || krbpasswordexpiration || krbprincipalk
ey || userpassword")(target = "ldap:///uid=*,cn=deleted users,cn=accounts,cn=
provisioning,dc=cgparente,dc=local")(targetfilter = "(objectclass=posixaccoun
t)")(version 3.0;acl "permission:System: Reset Preserved User password";allow
(read,search,write) groupdn = "ldap:///cn=System: Reset Preserved User passw
ord,cn=permissions,cn=pbac,dc=cgparente,dc=local";)
Example:
user "example" is member of admin groups:
ipa group-show admins
Group name: admins
Description: Account administrators group
GID: 142600000
Member users: admin, example
Member of groups: ad_users
kinit example
Password for example:
ipa user-del test --preserve
ipa: ERROR: Insufficient access: Insufficient 'write' privilege to the 'krbLastPwdChange' attribute of entry 'uid=test,cn=deleted users,cn=accounts,cn=provisioning,dc=cgparente,dc=local'
ipa role-add-member "User Administrator" --user=example
kinit example
ipa user-del test --preserve
Works.
Comment 2Florence Blanc-Renaud
2017-12-04 08:12:20 UTC
The behavior described by German is reproduced. Will check with the team if it is expected or if the role was mistakenly forgotten for the admins group.
Comment 3Florence Blanc-Renaud
2017-12-21 18:39:27 UTC
The file install/updates/30-provisioning.update defines the following acis that are specific to the admin user, but should be rather granted to the admins group:
dn: cn=staged users,cn=accounts,cn=provisioning,$SUFFIX
aci: (targetattr="userPassword || krbPrincipalKey")(version 3.0; acl "Search existence of password and kerberos keys"; allow(read, search) userdn = "ldap:///uid=admin,cn=users,cn=accounts,$SUFFIX";)
dn: cn=deleted users,cn=accounts,cn=provisioning,$SUFFIX
aci: (targetattr="userPassword || krbPrincipalKey || krbPasswordExpiration || krbLastPwdChange")(version 3.0; acl "Admins allowed to reset password and kerberos keys"; allow(read, search, write) userdn = "ldap:///uid=admin,cn=users,cn=accounts,$SUFFIX";)
Comment 4Florence Blanc-Renaud
2018-01-02 15:23:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:3187