Bug 747709 - non-admin user details browse issue
Summary: non-admin user details browse issue
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.1
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: ---
: ---
Assignee: Lukas Krejci
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: rhq42
TreeView+ depends on / blocked
 
Reported: 2011-10-20 20:12 UTC by Simeon Pinder
Modified: 2012-02-07 19:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 19:28:36 UTC


Attachments (Terms of Use)
non admin user ..loading.. (20.36 KB, image/png)
2011-10-20 20:50 UTC, Simeon Pinder
no flags Details

Description Simeon Pinder 2011-10-20 20:12:44 UTC
Description of problem:
When logged in as a non-admin user, if you browse the logged in user's details, you get "Loading... " screen. See attached screenshot.

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


How reproducible:
Everytime.

Steps to Reproduce:
1. Create a non-admin user account, 'anotherUser'.
2. Login with that user and attempt to navigate to Administration->Security>Users>anotherUser
3. User details may flash then "Loading...." message perists.
  
Actual results:
Unable to see current user's details and "Loading...." message perists.

Expected results:
Show user details or messsage indicating why not.

Additional info:

Comment 1 Simeon Pinder 2011-10-20 20:50:19 UTC
Created attachment 529386 [details]
non admin user ..loading..

Comment 2 Lukas Krejci 2011-10-21 11:53:11 UTC
commit 9e6373c10f89f61d889fee5244e4c8b5c41506ab
Author: Lukas Krejci <lkrejci>
Date:   Fri Oct 21 13:42:46 2011 +0200

    BZ 747709 - Making the user editor show itself for non-admin users.
    The logic for determining if LDAP auth is enabled has been moved
    from the GUI to an (unprivileged) SLSB method so that the editor
    doesn't require MANAGE_SETTINGS only to figure this thing out.

Comment 3 Mike Foley 2012-02-07 19:28:36 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE


Note You need to log in before you can comment on or make changes to this bug.