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.
Created attachment 1177517[details]
filtering from satellite for one role.
Description of problem:
When creating a filter allowing a user only to see things named ~ oss* ,
he is then only able to see things named oss* troughout the menus.
However if he press a activation key, and then in the url (as they are in sequence) select a number,he would not normally be able to see ie he has access to AK 1 normally and then he types 2 for the fun of it then he will see the number 2 AK even tough he should not be able to, and from that he can click host collections, and from that he can clone a host collection he would normally not have access to, and that way get access to all hosts under that collection and be able to change settings install packages and more on them.
Activation keys are of cause public if you have the right ORG id, and it will let you register a server, however it should not let you access other parts of the org that would normally be filtered out for you.
This way you effectively sets all filters out of action,
Version-Release number of selected component (if applicable):
6.2.0 beta 2
How reproducible:
Always.
Steps to Reproduce:
1. Create restrective filter that only allows you to see AK and more starting with name oss* or others using the ~ in the filter.
2. test what you can see.
3.
Actual results:
You can see every thing in the ui like were intended, however by modifying the url under activation keys, you can get access to other persons activation keys starting with something else than oss* that you normally would not be able to see nor edit due to the filtering.
Expected results:
permission denied for the access key you should not have access to due to the filter.
Additional info:
Filter attached.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Created attachment 1177517 [details] filtering from satellite for one role. Description of problem: When creating a filter allowing a user only to see things named ~ oss* , he is then only able to see things named oss* troughout the menus. However if he press a activation key, and then in the url (as they are in sequence) select a number,he would not normally be able to see ie he has access to AK 1 normally and then he types 2 for the fun of it then he will see the number 2 AK even tough he should not be able to, and from that he can click host collections, and from that he can clone a host collection he would normally not have access to, and that way get access to all hosts under that collection and be able to change settings install packages and more on them. Activation keys are of cause public if you have the right ORG id, and it will let you register a server, however it should not let you access other parts of the org that would normally be filtered out for you. This way you effectively sets all filters out of action, Version-Release number of selected component (if applicable): 6.2.0 beta 2 How reproducible: Always. Steps to Reproduce: 1. Create restrective filter that only allows you to see AK and more starting with name oss* or others using the ~ in the filter. 2. test what you can see. 3. Actual results: You can see every thing in the ui like were intended, however by modifying the url under activation keys, you can get access to other persons activation keys starting with something else than oss* that you normally would not be able to see nor edit due to the filtering. Expected results: permission denied for the access key you should not have access to due to the filter. Additional info: Filter attached.