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.
Description of problem:
If a user tries to access a page to which s/he has no permissions, an error should bubble up to the admin-level notification view.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Login as admin; visit the roles page and copy the URL; put it aside.
2. Create a user with only System rights. Login with this user
3. Paste in the URL which goes to the roles page and attempt to access it.
4. Logout and log back in as admin
5. Go to notifications
Actual results:
User gets permission denied
Nothing sent to notifications.
Expected results:
We should log invalid access attempts in notifications. Such notifications do not necessarily need to be accessible from said user's notifications view, but should be available to any admins. Something like
"Permission denied to page 'katello/roles' for user 'bobbytables'
Additional info:
Beyond being a catch for 'devious' behavior, this might be useful for noting legitimate attempts, i.e., perhaps there's a wiki somewhere that tells users they need to access $foo URL. They click it, login, and are greeted with a permission denied. An admin seeing a slew of these in the notifications log might be able to quickly determine whether a user is legitimately lacking proper permissions.
Logfile is fine but I really don't think this should create popup notification messages for admins of the site. This could end up causing notification spam and would generally be considered very annoying.
If someone was running a script to find vulnerabilities in the site you could get 1000s of notifications.
Permission denied errors should be logged but NOT stored as a notif