mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-05-04 12:13:19 +00:00
Billy Tat
27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
---
|
|
title: Role-Based Access Control (RBAC)
|
|
weight: 20
|
|
---
|
|
|
|
Within Rancher, each person authenticates as a _user_, which is a login that grants you access to Rancher. As mentioned in [Authentication]({{<baseurl>}}/rancher/v2.6/en/admin-settings/authentication/), users can either be local or external.
|
|
|
|
After you configure external authentication, the users that display on the **Users** page changes.
|
|
|
|
- If you are logged in as a local user, only local users display.
|
|
|
|
- If you are logged in as an external user, both external and local users display.
|
|
|
|
## Users and Roles
|
|
|
|
Once the user logs in to Rancher, their _authorization_, or their access rights within the system, is determined by _global permissions_, and _cluster and project roles_.
|
|
|
|
- [Global Permissions]({{<baseurl>}}/rancher/v2.6/en/admin-settings/rbac/global-permissions/):
|
|
|
|
Define user authorization outside the scope of any particular cluster.
|
|
|
|
- [Cluster and Project Roles]({{<baseurl>}}/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/):
|
|
|
|
Define user authorization inside the specific cluster or project where they are assigned the role.
|
|
|
|
Both global permissions and cluster and project roles are implemented on top of [Kubernetes RBAC](https://kubernetes.io/docs/reference/access-authn-authz/rbac/). Therefore, enforcement of permissions and roles is performed by Kubernetes.
|