Red Hat Bugzilla – Bug 1229210
Logging in with restricted user(Automate/Log) gives Authentication failed message
Last modified: 2016-06-29 10:56:31 EDT
Created attachment 1036266 [details] Restricted user error Description of problem: Logging in with restricted user(Automate/Log) gives Authentication failed message Version-Release number of selected component (if applicable): 5.4.0.5.20150605150206_7daa1a8 How reproducible: 100% Steps to Reproduce: 1. Create a new role and only give it the Automate => Log permission 2. Add a new group and assign the role to the group 3. Add a new user and assign the used to the group 4. Try to log in as the new user Actual results: "The user's role is not authorized for any access, please contact the administrator!" message is displayed. Refer the screenshot and evm.log for more details Expected results: Logged in and placed on the Automate => Log page. Additional info: evm.log: ======= [----] E, [2015-06-08T05:25:06.523946 #2654:105deac] ERROR -- : MIQ(dashboard_controller-authenticate): The user's role is not authorized for any access, please contact the administrator!
https://github.com/ManageIQ/manageiq/pull/5830
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/efe708216fc510d6320b63b6bcb922c0cd2ed65f commit efe708216fc510d6320b63b6bcb922c0cd2ed65f Author: Milan Zazrivec <mzazrivec@redhat.com> AuthorDate: Mon Dec 14 15:20:13 2015 +0100 Commit: Milan Zazrivec <mzazrivec@redhat.com> CommitDate: Mon Dec 14 15:20:13 2015 +0100 Add Automate -> Log start page Users who are (via role) allowed to view automate logs only will land on this page upon login. Otherwise, these users would not be able to log in at all. https://bugzilla.redhat.com/show_bug.cgi?id=1229210 db/fixtures/miq_shortcuts.yml | 5 +++++ 1 file changed, 5 insertions(+)
Good to go. Verified and working fine in 5.6.0.4-beta2.3.20160421172650_719e256
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/RHBA-2016:1348