| |||||||||||||||||||||||||||||||||
Identify common vCenter Server privileges and roles Privileges are independent units of security in vSphere. Each privilege:
|
|||||||||||||||||||||||||||||||||
Privileges define individual rights that a user requires to perform actions and read properties. A role is a named set of one or more privileges and it is used to grant users or groups access to managed entities. A role is normally defined for a group of people who have common responsibilities in the system, for example, administrators. Each role can have zero to multiple privileges. Roles provide a way to aggregate all the individual privileges that are required to perform a higher-level task, such as administer a virtual machine. With these roles you can assign permissions on vSphere objects. An object is an entity upon which actions are performed. Examples of objects are datacenters, folders, resource pools, clusters, hosts, and virtual machines. vCenter Server and ESXi hosts provide two default role types: System roles Permanent roles. You cannot edit the privileges associated with these roles. You can also create new, user-defined roles.
|
|||||||||||||||||||||||||||||||||
When you assign a user or group permissions, you pair the user or group (principal) with a role and associate that pairing with an inventory object. A single user might have different roles for different objects in the inventory. For example, if you have two resource pools in your inventory, Pool A and Pool B, you might assign a particular user the Virtual Machine User role on Pool A and the Read Only role on Pool B. The roles created on an ESX/ESXi host are separate from the roles created on a vCenter Server system. When you manage a host using vCenter Server, the roles created through vCenter Server are available. If you connect directly to the host using the vSphere Client, the roles created directly on the host are available. In vSphere, a permission consists of a user or group and an assigned role for an inventory object, such as a virtual machine or ESX/ESXi host. Permissions grant users the right to perform the activities specified by the role on the object to which the role is assigned. The list of privileges is the same for both ESXi and vCenter Server, and you use the same method to configure permissions. You can create roles and set permissions through a direct connection to the ESXi host. When you assign a permission to an object, you can choose whether each permission propagates down the object hierarchy. Permissions defined for a child object always override the permissions that are propagated from parent objects. Most inventory objects inherit permissions from a single parent object in the hierarchy. Some, like virtual machines inherit permissions from both the parent virtual machine folder and the parent host, cluster, or resource pool simultaneously. To restrict a user’s privileges on a virtual machine, you must set permissions on both the parent folder and the parent host, cluster, or resource pool for that virtual machine. Objects can have multiple permissions. |
|||||||||||||||||||||||||||||||||
References:
|
|||||||||||||||||||||||||||||||||
|