Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Ok I already fixed a quick workaround for the similar problem:
1634bdc 736384 - workaround for perm. denied for rhsm registration
but since this is blocker I am going to provide full solution. Taking.
I wonder what the permission should look like.
RHSM is requesting list of owners for given user1, it is authorized as user2. So I am assuming the following:
a) user1 = user2
b) user1/2 can register system
I am going to implement both there permission rules and correct the behavior.
@Bryan - Sorry I fixed it last week, but forgot to do the push. I did it but it failed...
bed93c3 736438 - implement permission check for list_owners
311bf3b 736438 - move list_owners from orgs to users controller
Pushed.