One of the key features that Rancher adds to Kubernetes is centralized user authentication. This feature allows your users to use one set of credentials to authenticate with any of your Kubernetes clusters.

This centralized user authentication is accomplished using the Rancher authentication proxy, which is installed along with the rest of Rancher. This proxy authenticates your users and forwards their requests to your Kubernetes clusters using a service account.

External vs. Local Authentication

The Rancher authentication proxy integrates with the following external authentication services. The following table lists the first version of Rancher each service debuted.

Auth Service Available as of
Microsoft Active Directory v2.0.0
GitHub v2.0.0
Microsoft Azure AD v2.0.3
FreeIPA v2.0.5
OpenLDAP v2.0.5
Microsoft AD FS v2.0.7
PingIdentity v2.0.7
Keycloak v2.1.0
Okta v2.2.0

However, Rancher also provides local authentication.

In most cases, you should use an external authentication service over local authentication, as external authentication allows user management from a central location. However, you may want a few local authentication users for managing Rancher under rare circumstances, such as if your external authentication provider is unavailable or undergoing maintenance.

Users and Groups

Rancher relies on users and groups to determine who is allowed to log in to Rancher and which resources they can access. When authenticating with an external provider, groups are provided from the external provider based on the user. These users and groups are given specific roles to resources like clusters, projects, multi-cluster apps, and global DNS providers and entries. When you give access to a group, all users who are a member of that group in the authentication provider will be able to access the resource with the permissions that you’ve specified. For more information on roles and permissions, see Role Based Access Control.

Note: Local authentication does not support creating or managing groups.

For more information, see Users and Groups

External Authentication Configuration and Principal Users

Configuration of external authentication requires:

  • A local user assigned the administrator role, called hereafter the local principal.
  • An external user that can authenticate with your external authentication service, called hereafter the external principal.

Configuration of external authentication affects how principal users are managed within Rancher. Follow the list below to better understand these effects.

  1. Sign into Rancher as the local principal and complete configuration of external authentication.

    Sign In

  2. Rancher associates the external principal with the local principal. These two users share the local principal’s user ID.

    Principal ID Sharing

  3. After you complete configuration, Rancher automatically signs out the local principal.

    Sign Out Local Principal

  4. Then, Rancher automatically signs you back in as the external principal.

    Sign In External Principal

  5. Because the external principal and the local principal share an ID, no unique object for the external principal displays on the Users page.

    Sign In External Principal

  6. The external principal and the local principal share the same access rights.