Red Hat Bugzilla – Bug 1192203
We shouldn't treat users being in the wrong org as an error when they try to navigate the UI
Last modified: 2017-02-23 15:31:43 EST
Description of problem: I see this message a lot when I poke around Satellite. "403 - Permission Denied Please choose an organization using the selector located at the far left of the menu." I'm logged in as the admin, do I really not have permissions to view what I tried to click on? The message doesn't seem entirely accurate. If there's really nothing useful we can show when this triggers, could we replace this generic sounding error message (that makes it sound like you did something wrong) with a message that simply tells them to pick a specific Org and embeds the org picker where they can choose one right there, without having to go up to the org picker and fiddling with it? Version-Release number of selected component (if applicable): 6.0.6
Created attachment 991146 [details] 403 - Permission Denied
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Eric, Assigning to you as I believe you were recently working on some improvements to this area.
Connecting redmine issue http://projects.theforeman.org/issues/8387 from this bug
See https://github.com/Katello/katello/pull/4847
VERIFIED: # rpm -qa | grep foreman foreman-1.7.2.8-1.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.2-1.el6_6sat.noarch foreman-compute-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_docker-1.2.0.2-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.1-1.el6_6sat.noarch foreman-proxy-1.7.2.3-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch foreman-vmware-1.7.2.8-1.el6_6sat.noarch foreman-libvirt-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_abrt-0.0.5-2.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch rubygem-hammer_cli_foreman-0.1.4.6-1.el6_6sat.noarch foreman-selinux-1.7.2.8-1.el6_6sat.noarch foreman-debug-1.7.2.8-1.el6_6sat.noarch foreman-gce-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.0.8-2.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.5-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-postgresql-1.7.2.8-1.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch foreman-ovirt-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.8-1.el6_6sat.noarch
*** Bug 1191912 has been marked as a duplicate of this bug. ***
*** Bug 1154370 has been marked as a duplicate of this bug. ***
This bug is slated to be released with Satellite 6.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592