Red Hat Bugzilla – Bug 833517
[RFE] [Web UI] Add support for DNS per-domain permissions
Last modified: 2013-02-21 04:16:00 EST
This bug is created as a clone of upstream ticket: https://fedorahosted.org/freeipa/ticket/2851 Ticket #2511 adds support for per-domain DNS permissions. Administrator can now assign a user to `managedBy` attribute to make him able read/write selected DNS zone. To find out if a logged user have read/write privilege to some zone, the following query can be run: {{{ ipa dnszone-find --man-by-users=<user> }}}
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Fixed upstream: 14ac2193fec38b6f87dcf04b0c365d01805b0cae
Verifying
ipa version: ipa-server-3.0.0-8.el6.x86_64 how to verify: 1.create a new user 2.add DNS zone 3.add permission via DNS 4.add privilege 6.add role 7.login as new user 8.verify that can list zone managed by user ,cannot list zone not managed by user 9.verify that can't add a new zone 10.verify that can't delete zone managed by user 11.verify that can enable&disable zone managed by user 12.verify that can't modify global configuration 13.verify that can't remove permission managed by user in permission page 14.verify that can't remove permission in the dns attribute to manage this zone 15.login as admin 16.verify that once permission is removed via DNS ,the permission is moved as well 17.verify that if permission is deleted then the dns managedby attribute is not set(able to add again , then delete it) 18.verify that if permission is deleted then the user can no longer access the zone 19.remove dns zone 20.remove the user 21.remove privilege 22.remove role
xdong verified taking steps above
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. http://rhn.redhat.com/errata/RHSA-2013-0528.html