Citrix Hypervisor

Role-based access control

January 9, 2023

Contributed by:

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:

Join the domain. For more information, see Enabling external authentication on a pool.
Add an Active Directory user or group to the pool. This becomes a subject. For more information, see To add a subject to RBAC.
Assign (or change) the subject’s RBAC role. For more information, see To assign an RBAC role to a subject.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Role-based access control

January 9, 2023

Contributed by:

January 9, 2023

Contributed by:

Role-based access control

RBAC process

In this article