New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 645097 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

User Role set to not allow Read Org Units can still see names of Org Units in Kiosk Management

Reported by bbackh...@mylivingwindow.com, Sep 8 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. Create role with only Manage Kiosk Devices selected, all others off
2. Create several OUs
3. Assign user to one OU
4. Assign role to user
5. Login as user and go to Kiosk Settings (I'm using Chrome Sign Builder as my Kiosk single app) to select the OU to manage
6. Super-admin should see all OUs.  Limited Role user should only see the name of the OUs to which it is a member (one in this case)

What is the expected behavior?
Limited Role and OU user should only see names of member OUs.  All other names of OUs should not be visible to this limited user.

What went wrong?
Limited Role user which is a member of only one sub OU can view names of all OUs

Did this work before? No 

Chrome version: 52.0.2743.116  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

My intent is to have clients as users in my domain and set into a role able to manage their own Kiosk device, but they should not be allowed to see the names of any other clients. They should only be able to see their own OU name.  I ran this question through Enterprise Support first, before filing this enhancement request.
 

Comment 1 by dskaram@google.com, Sep 9 2016

Cc: royans@chromium.org
Status: WontFix (was: Unconfirmed)
This is currently known. Adding Royans in case he has any input. In all cases, this tracker is not the place for this request (only client bugs are tracked here). This should go on the server team's internal tracker.

Royans, please advise on how to file this FR for the proper team internally.
Thanks everyone.

Since I won't be able to see status or progress in the internal tracker
system, will there be any way for me to follow status?

I did try to diligently search the client-tracker list for anything similar
and did not see anything similar, my apologies.

Brent

Comment 3 by dskaram@google.com, Sep 10 2016

Owner: royans@chromium.org
Thanks Brent, when we do have updates, we'll put them back here.
Hi,

Wondering if any activity is planned to resolve this issue?

Thanks, Happy New Year,
Brent

Sign in to add a comment