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.
Bug 829794 - Trying to access many top-level menu items as a user w/ no rights throws ISEs rather than permission denied.
Summary: Trying to access many top-level menu items as a user w/ no rights throws ISEs...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-07 14:59 UTC by Corey Welton
Modified: 2019-09-25 20:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Access to pages without appropriate permissions resulted in a 500 Internal Server Error message. This fix allows users without permissions to only access systems but denies other pages with 403 Permission Denied.
Clone Of:
Environment:
Last Closed: 2012-10-24 14:22:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description Corey Welton 2012-06-07 14:59:35 UTC 
Description of problem:
When a user with no rights attempts to access certain menu items (i.e., perhaps by a bookmark) that said user does not have rights to, ISEs are thrown. User should be getting permission denied messages, or at very least, it should handle the situation gracefully.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Login as admin. Copy/bookmark the URL for any of the main top-level menu items -- Content Management, Systems, Organizations, etc.
2.  Create a user, "norights" which has no associated roles.
3.  Logout and log back in with user norights.
4.  Paste in your URL or visit bookmark, to try and access some of those pages.
  
Actual results:

500 Internal Server Error

Sorry about that! It seems something went wrong. If you continue having trouble with this, please contact an Administrator.

You might want to log out and log back in again to clear your cookies.
Error:

    undefined method `allowed_organizations' for nil:NilClass



Expected results:

Situation is handled gracefully - no ISEs.

Additional info:
Comment 2 Pavel Pokorny 2012-07-18 08:17:09 UTC 
Katello 049d74c361:

As a user with no assigned roles I can access only systems. All other pages I tried (directly through URL) are 403 - Permission Denied.

So I think it is fixed. What page exactly was 500?
Comment 4 Corey Welton 2012-09-17 15:47:54 UTC 
Maybe this got fixed with the UI redesign. It no longer occurs. User no longer gets ISEs.

CloudForms System Engine Version: 1.1.12-7.el6cf
Comment 5 Mike McCune 2012-10-24 14:22:04 UTC 
closing, currentrelease since these seemingly got missed in the 1.0.1 errata
Note You need to log in before you can comment on or make changes to this bug.