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:
When we create RBAC permission, with CLI or WebUI, we can create permission with empty target attribute list. 

This will act as we didn't permit any attributes to be accessed, so permission without attributes won't do anything.


Version-Release number of selected component (if applicable):
RHEL 8.6
ipa-server-4.9.8-7
389-ds-base-1.4.3.28-6

How reproducible:
always

Expected results:
we should probably add a warning that empty target attributes are not really meaningful. Or just make this mandatory.

Additional info:

Linked to upstream issue https://pagure.io/freeipa/issue/9188

Fixed upstream
master:
https://pagure.io/freeipa/c/dc73813b8afccb82b513c49b29de35b7864819b6

Note to QA: the xmlrpc tests already check that the warning is displayed:

ipatests/test_xmlrpc/test_old_permission_plugin.py::test_old_permission
ipatests/test_xmlrpc/test_permission_plugin.py::test_permission_bindtype and ::test_permission_filters
ipatests/test_xmlrpc/test_privilege_plugin.py::test_privilege

Fixed upstream
ipa-4-10:
https://pagure.io/freeipa/c/499f71729b8689d40608d9c99db703eb2c00a934

ipa-4-9:
https://pagure.io/freeipa/c/b31631ad69f72fb42b5091375df8021580f8139a

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 (idm:client and idm:DL1 bug fix and enhancement update), 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-2023:2794