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.
DescriptionDmitry Zhukovski
2017-10-12 06:52:24 UTC
Description of problem:
Restrict edit_params & create_params to set host parameters only on hosts that user owns
Version-Release number of selected component (if applicable):
6.2.12
How reproducible:
everytime
Steps to Reproduce:
1. Define that filter
Host build_hosts, create_hosts lifecycle_environment = "SomeEnv"
Host destroy_hosts, edit_hosts, view_hosts owner = <someuser>
Host power_hosts owner = <someuser>
Parameter edit_params, create_params none
Domain view_domains name = <somedomain>
2.Create new parameters on a hostname that is NOT owned by someuser
https://satellite/api/hosts/hostname/parameters
with json for example.
{
"name": "groups",
"value": "<group1>"
}
3.
Actual results:
POST is succesful even that hostname is not belonging to someuser and not visible on All hosts page by that user
Expected results:
User is restricted to change/add parameters only on his own hosts
Additional info:
Thanks Dmitry for report, I believe this is a duplicate of BZ 1384035 which tracks it not only for parameters but all resources. I'm marking it as a duplicate, please reattach the case. If I misunderstood, please let me know or reopen.
*** This bug has been marked as a duplicate of bug 1384035 ***