Citrix Hypervisor

Role-based access control

The Role-Based Access Control (RBAC) feature in Citrix Hypervisor allows you to assign users, roles, and permissions to control who has access to your Citrix Hypervisor and what actions they can perform. The Citrix Hypervisor RBAC system maps a user (or a group of users) to defined roles (a named set of permissions). The roles have associated Citrix Hypervisor permissions to perform certain operations.

Permissions are not assigned to users directly. Users acquire permissions through roles assigned to them. Therefore, managing individual user permissions becomes a matter of assigning the user to the appropriate role, which simplifies common operations. Citrix Hypervisor maintains a list of authorized users and their roles.

RBAC allows you to restrict which operations different groups of users can perform, reducing the probability of an accident by an inexperienced user.

RBAC also provides an Audit Log feature for compliance and auditing.

RBAC depends on Active Directory for authentication services. Specifically, Citrix Hypervisor keeps a list of authorized users based on Active Directory user and group accounts. As a result, you must join the pool to the domain and add Active Directory accounts before you can assign roles.

The local super user (LSU), or root, is a special user account used for system administration and has all rights or permissions. The local super user is the default account at installation in Citrix Hypervisor. The LSU is authenticated through Citrix Hypervisor and not through an external authentication service. If the external authentication service fails, the LSU can still log in and manage the system. The LSU can always access the Citrix Hypervisor physical host through SSH.

RBAC process

The following section describes the standard process for implementing RBAC and assigning a user or group a role:

  1. Join the domain. For more information, see Enabling external authentication on a pool.

  2. Add an Active Directory user or group to the pool. This becomes a subject. For more information, see To add a subject to RBAC.

  3. Assign (or change) the subject’s RBAC role. For more information, see To assign an RBAC role to a subject.

Role-based access control