Bug 1004412 - When assigning role to user which is not allowed view children on network, then user can't see this network.
Summary: When assigning role to user which is not allowed view children on network, th...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.3.0
Assignee: Nobody
QA Contact:
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-04 15:04 UTC by Ondra Machacek
Modified: 2016-02-10 19:48 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-09 08:10:43 UTC
oVirt Team: Network
Target Upstream Version:


Attachments (Terms of Use)

Description Ondra Machacek 2013-09-04 15:04:40 UTC
Description of problem:
User with role that can't view children on network, can't see that network.

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

How reproducible:
always

Steps to Reproduce:
1. Create network.
2. Assign some role that is not allowed to view children on network to user.
   (ie. VmCreator, DiskCreator, ..)
3. As user check /api/networks

Actual results:
user can't see network

Expected results:
user can see network

Additional info:

Comment 1 Moti Asayag 2013-09-09 08:10:43 UTC
This is intentional by the design of the vnic profiles feature as described on [1]:

NOTE: the permissions used below besides the direct one, and the VM/Template one, must allow the user to view the child objects

    The user has direct user permissions on the VNIC profile
    The user has user permissions on the VNIC profile's network 
    ...

This is due to the fact that the network is and administrative entity and should be viewed from the admin api and will be viewed on the user api if any of the conditions specified on [1] are met.



[1] http://www.ovirt.org/Features/Vnic_Profiles#VNIC_Profiles


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