Bug 912267

Summary: [RFE] per DC directory services
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: ovirt-engineAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, iheim, jkt, lpeer, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-01 10:36:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jiri Belka 2013-02-18 09:04:03 UTC 
Description of problem:

Split from BZ890506.

* per DC directory services - company managing RHEV-M could be personally different from those managing individual VMs. So RHEV-M services provider should be able to give access to specific sysadmins to a DC, but other permissions inside this DC should be managed by the owner (sysadmins) who can delegate additional permissions to their own users/groups in their own directory service.

Simon Grinberg 2012-12-27 09:36:48 EST 
> not sure what the right model is for directory services

I would say tenant as well. The challenge is to understand based on -TBD- to which tenant the user belongs too. 

If I'll take salesforce model, they do not provide a drop down list, but rather user has to login with full UPN, if we enforce the same we can use the domain part of the UPN to select the directory to authenticate against. Mapping to be provided by the admin.
Comment 1 Itamar Heim 2013-12-01 10:36:57 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.