<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.6 (unsupported)</button>

- [Latest](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/latest/installing/oidc-google)
- [Version 1.16](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.16/installing/oidc-google)
- [Earlier versions (unsupported)](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/getting-support.md.txt#version-support)

<br />

Learn how to configure [OpenID Connect](https://developers.google.com/identity/protocols/OpenIDConnect) (OIDC) in
Google Distributed Cloud and use Google as the OpenID Provider.

For an overview of the Google Distributed Cloud authentication flow, see
[Authentication](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/identity-manage.md.txt).
See the following topics to learn how to configure OIDC with
other OpenID providers:

- [Active Directory Federation Services](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-adfs.md.txt)
- [Any OpenID provider](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/connect-oidc.md.txt)

## Overview

Google Distributed Cloud supports OIDC as one of the
authentication mechanisms for interacting with a cluster's Kubernetes API
server. With OIDC, you can manage access to Kubernetes clusters by using the
standard procedures in your organization for creating, enabling, and disabling
user accounts.

There are two ways that users can authorize their accounts:

- Use the Google Cloud CLI to initiate the OIDC flow and
  obtain user authorization through a browser-based consent page.

- Use Google Cloud console to initiate the OIDC authentication flow.

## Before you begin

- This topic assumes you are familiar with the following authentication and
  OpenID concepts:

  - [OAuth 2.0](https://oauth.net/2/)
  - [OpenID Connect](https://openid.net/connect/)
  - [scopes](https://openid.net/specs/openid-connect-core-1_0.html#ScopeClaims)
  - [claims](https://openid.net/specs/openid-connect-core-1_0.html#IDToken).
- The Google OpenID provider does not support groups. When you use Kubernetes
  role-based access control (RBAC) to
  [grant roles to authenticated users](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#rbac_policy),
  you must grant roles to each individual user, not a group.

- Headless systems are unsupported. A browser-based authentication flow is used
  to prompt you for consent and authorize your user account.

- To authenticate through the Google Cloud console, each cluster that you want to
  configure for OIDC authentication must be
  [registered with Google Cloud](https://docs.cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster).

## Personas

This topic refers to three personas:

- *Organization administrator*: This person chooses an OpenID provider and
  registers client applications with the provider.

- *Cluster administrator*: This person creates one or more clusters and
  creates authentication configuration files for developers who use the
  clusters.

- *Developer*: This person runs workloads on one or more clusters and uses OIDC
  to authenticate.

## Creating redirect URLs

This section is for [organization administrators](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#personas).

You must create redirect URLs for both the gcloud CLI and
Google Cloud console that the OpenID provider can use to return ID tokens.

### gcloud CLI redirect URL

Google Cloud CLI is installed on each developer's local machine and includes the
gcloud CLI. You can specify a port number greater than 1024 to use for the
redirect URL:

```
http://localhost:[PORT]/callback
```

where <var translate="no">\[PORT\]</var> is your port number.

When you configure the Google OpenID provider, specify
`http://localhost:[PORT]/callback` as one of your redirect URLs.

### Google Cloud console redirect URL

The redirect URL for Google Cloud console is:

```
https://console.cloud.google.com/kubernetes/oidc
```

When you configure the Google OpenID provider, specify
`https://console.cloud.google.com/kubernetes/oidc` as one of your redirect URLs.

### Configuring your consent screen

In this section, you configure Google's OAuth consent screen. When a developer
in your organization initiates authentication to a cluster, they are taken
to this consent screen. At that time, they prove their identity to Google and
give Google permission to create a token that provides identifying information
to the OAuth client. In the context of this topic, the OAuth client is either
the gcloud CLI or Google Cloud console.

1. Go to the **OAuth consent screen** page in Google Cloud console.

   [Configure the OAuth consent screen](https://console.cloud.google.com/apis/credentials/consent)
2. Select **Internal** , and click **Create**.

3. For **Application type** , select **Internal**.

4. For **Application name** , enter a name of your choice. Suggestion: `bare
   metal`.

5. Under **Authorized domains** , add `google.com`.

6. Fill in additional fields as you see fit.

7. Click **Save**.

## Registering a client application with Google

In this section, you register Google Distributed Cloud with Google, so that
Google can act as the OpenID provider for developers in your organization. As
part of the registration, you must supply the two redirect URLs that you
[created previously](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#redirect_url_plugin).

1. Go to the **Credentials** page in Google Cloud console.

   [Go to the Credentials page](https://console.cloud.google.com/apis/credentials)
2. Click **Create credentials** , and select **OAuth client ID**.

3. For **Application type** , select **Web application**.

4. For **Name**, enter a name of your choice.

5. Under **Authorized redirect URIs** , add your two redirect URLs. Recall that
   you created a
   [redirect URL for the gcloud CLI](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#redirect_url_plugin)
   and a
   [redirect URL for Google Cloud console](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#redirect_url_console).

6. Click **Create**.

7. You are given a client ID and a client secret. Save these for later use.

## Populating the `oidc` specification in Google Distributed Cloud configuration file

This section is for [cluster administrators](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#personas).

Before you create a cluster, you generate a Google Distributed Cloud
configuration file using `bmctl create config`. The configuration
includes the following `oidc` specification. You must populate
`oidc` with the values specific to your provider:

```
authentication:
  oidc:
    issuerURL:
    kubectlRedirectURL:
    clientID:
    clientSecret:
    username:
    usernamePrefix:
    group:
    groupPrefix:
    scopes:
    extraParams:
    proxy:
    deployCloudConsoleProxy:
    certificateAuthorityData:
```

- `issuerURL`: Set this to `"https://accounts.google.com"`. Client applications, like the gcloud CLI and Google Cloud console, send authorization requests to this URL. The Kubernetes API server uses this URL to discover public keys for verifying tokens.
- `kubectlRedirectURL`: Required. The redirect URL that you [configured previously](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#redirect_url_plugin) for the gcloud CLI.
- `clientID`: ID for the client application that makes authentication requests to the OpenID provider. Both the `gcloud` CLI and Google Cloud console use this ID. You were given this ID when you [registered your client application](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#register_client_app) with Google.
- `clientSecret`: Secret for the client application. Both the gcloud CLI and Google Cloud console use this secret. You were given this ID when you [registered your client application](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#register_client_app) with Google.
- `username`: Set this to `"email"`.
- `usernamePrefix`: Optional. Prefix prepended to username claims to prevent clashes with existing names. If you do not provide this field, and `username` is a value other than `email`, the prefix defaults to `issuerurl#`. You can use the value `-` to disable all prefixing.
- `group`: Leave this blank.
- `groupPrefix`: Leave this blank.
- `scopes`: Set this to `"email"`
- `extraParams`: Set this to `"prompt=consent,access_type=offline"`.
- `proxy`: Optional. Starting with Google Distributed Cloud 1.6.1, you can specify a proxy server to use for the cluster to connect to your OIDC provider, if applicable. For example: `http://user:password@10.10.10.10:8888`. If left blank, this defaults to no proxy.
- `deployCloudConsoleProxy`: Set this to `false`.
- `certificateAuthorityData`: Leave this blank.

## Creating an RBAC policy for your cluster

This section is for [cluster administrators](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#personas).

After you create a cluster, use
[Kubernetes role-based access control (RBAC)](https://kubernetes.io/docs/reference/access-authn-authz/rbac/)
to grant access to authenticated cluster users. To grant access to resources in
a particular namespace, create a
[Role](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#role-example)
and a
[RoleBinding](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#rolebinding-example).
To grant access to resources across an entire cluster, create a
[ClusterRole](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#clusterrole-example)
and a
[ClusterRoleBinding](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#clusterrolebinding-example).

When you use Google as your OpenID provider, you must grant access to individual
users. It does not work to grant access to groups. This is because the token
that the Google OpenID provider returns does not have any information about the
the groups that an individual user belongs to.

For example, suppose you want jane@example.com to be able to view all Secret
objects across the cluster.

Here's a manifest for a ClusterRole named `secret-viewer`. A person who is
granted this role can get, watch, and list any Secret in the cluster.

```
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: secret-viewer
rules:
- apiGroups: [""]
  # The resource type for which access is granted
  resources: ["secrets"]
  # The permissions granted by the ClusterRole
  verbs: ["get", "watch", "list"]
```

Here is a manifest for a ClusterRoleBinding named `people-who-view-secrets`. The
binding grants the `secret-viewer` role to a user named `jane@example.com`.

```
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: people-who-view-secrets
subjects:
- kind: User
  name: jane@example.com
  apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: ClusterRole
  name: secret-viewer
  apiGroup: rbac.authorization.k8s.io
```

To create the ClusterRole, save the manifest to a file named
`secret-viewer-cluster-role.yaml`, and enter this command:

```
kubectl --kubeconfig [CLUSTER_KUBECONFIG] apply -f secret-viewer-cluster-role.yaml
```

where <var translate="no">\[CLUSTR_KUBECONFIG\]</var> is the kubeconfig file for your
cluster.

To create the ClusterRoleBinding, save the manifest to a file named
`secret-viewer-cluster-role-binding.yaml`, and enter this command:

```
kubectl --kubeconfig [CLUSTER_KUBECONFIG] apply -f secret-viewer-cluster-role-binding.yaml
```

## Installing the gcloud CLI

This section is for both [cluster administrators and developers](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#personas).

Cluster administrators who want to create cluster authentication configuration
files \& each developer or user who needs to authenticate with a cluster, must
install Google Cloud CLI on their own machine. The Anthos authentication commands
have been integrated into the gcloud CLI as the `anthos-auth`
[component](https://docs.cloud.google.com/sdk/docs/components.md.txt).

- If you have an old version of "Anthos Plugin for Kubectl", you must
  [uninstall that plugin](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#removing_old_plugins) before installing the `gcloud`
  CLI and `anthos-auth` component.

- If you have an existing version of the gcloud CLI, [install the latest
  version and the `anthos-auth` component](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google#installing_cloud_sdk).

### Removing old plugins

You must uninstall the old plugin before you can use the `anthos-auth`
component of gcloud CLI. You can check whether one of the past `kubectl`
based plugins exists on your machine by running the following command:

<br />

```
kubectl anthos version
```

<br />

- If the command responds with `Error: unknown command "anthos" for "kubectl"`,
  no plugin was found and you can skip to the next section.

- If a `1.0beta` version of the plugin was found, you must locate the plugin
  binary and delete it. Run the following command to list the location and then
  use that location to remove the binary from your machine:

  ```
  kubectl plugin list
  ```

### Installing gcloud CLI and the gcloud CLI

To install the gcloud CLI you must first first install gcloud CLI:

> [!IMPORTANT]
> **Important:** Using gcloud CLI with Google Distributed Cloud does not require you to have a Google account. If you have an account, sign in is optional but you do not need to run the `gcloud init` command.

1. [Install gcloud CLI](https://docs.cloud.google.com/sdk/docs.md.txt) but skip the `gcloud init` command.

2. Run the following commands to install the `anthos-auth` component:

   ```
   gcloud components update
   gcloud components install anthos-auth
   ```
3. Verify that the gcloud CLI was installed successfully by running either of
   the following commands:

   ```
   gcloud anthos auth
   gcloud anthos auth login
   ```

   Result: Each command should respond with details about the required
   arguments and available options.

## Creating and distributing the authentication configuration file

This section is for [cluster administrators](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#personas).

After you create a cluster, you create an authentication configuration file
for that cluster. You can configure multiple clusters in a single authentication
configuration file. You must provide each authentication configuration file to
the users who want to authenticate with each of those clusters.

### Creating the authentication configuration file

To create the authentication configuration file in
the current directory, run the following `gcloud` command:

```
gcloud anthos create-login-config --kubeconfig [CLUSTER_KUBECONFIG]
```

where <var translate="no">\[CLUSTER_KUBECONFIG\]</var> is the path of your cluster's
`kubeconfig` file. When you ran `bmctl create cluster` to create your
cluster, your
[`kubeconfig` file](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig)
was created.

Result: Your authentication configuration file, named
`kubectl-anthos-config.yaml`, is created in the current directory.

### Adding multiple clusters to the authentication configuration file

You can store the authentication configuration details for multiple clusters
within a single authentication configuration file.

You can use the following command to merge additional cluster
authentication details into an existing authentication configuration file. Given
an existing authentication configuration file, you can either merge or combine
additional cluster authentication details:

- Merge the additional cluster authentication details into that existing authentication configuration file.
- Combine the additional cluster authentication details into a new file.

For example, you might need to manage both the `anthos-config-1cluster.yaml`
and `anthos-config-3clusters.yaml` authentication configuration files to
accommodate the access needs of the multiple user groups in your organization.

To add additional clusters to your existing authentication configuration
file:

1. Ensure that each cluster has a unique name. If your clusters have the same
   names, you cannot combine them into the same authentication configuration
   file. Note that after a cluster is created, that cluster cannot be renamed.

2. Run the following `gcloud` command to merge or combine configuration details:

   ```
   gcloud anthos create-login-config --kubeconfig [CLUSTER_KUBECONFIG] \
   --merge-from [IN_AUTH_CONFIG_FILE] --output [OUT_AUTH_CONFIG_FILE]
   ```

   where
   - <var translate="no">\[CLUSTER_KUBECONFIG\]</var> specifies the `kubeconfig` file of
     the cluster that you want to add.

   - <var translate="no">\[IN_AUTH_CONFIG_FILE\]</var> specifies the path of the existing
     authentication configuration file that you want to merge with the
     additional cluster information.

   - <var translate="no">\[OUT_AUTH_CONFIG_FILE\]</var> specifies the path of the file where
     you want to store the merged authentication configuration:

     - Specify the same file as <var translate="no">\[IN_AUTH_CONFIG_FILE\]</var> to merge the additional cluster information into that existing file.
     - Specify a new path and filename to combine the authentication configuration details into a new file.

### Distributing the authentication configuration file

To enable your users to authenticate against your clusters, you must
provide them with access to one or more of the authentication configuration
files that you created. Note that the following steps use the default file name
and the location that are expected by the gcloud CLI. For information about
using alternate file names and locations, see
[Custom configuration](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#custom_configuration).

Consider distributing the authentication configuration files by:

- Hosting the file at an accessible URL. If you include the `--login-config`
  flag in the `gcloud anthos auth login` command, the gcloud CLI obtains
  the authentication configuration file from that location.

  Consider hosting the file on a secure host. See the
  [`--login-config-cert`](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#plugin_to_authenticate) flag of the gcloud CLI for
  more information about using PEM certificates for secure HTTPS access.
- Manually providing the file to each user. After users download the file, you
  must instruct them about how to store the file in the default location and
  with the default filename that the gcloud CLI expects.

  For example, users can run the following commands to store the authentication
  configuration file with the default `kubectl-anthos-config.yaml` filename and
  in the default location:

  ### Linux

  ```
  mkdir -p  $HOME/.config/google/anthos/
  cp [AUTH_CONFIG_FILE] $HOME/.config/google/anthos/kubectl-anthos-config.yaml
  ```

  where <var translate="no">\[AUTH_CONFIG_FILE\]</var> is the name of your authentication
  configuration file. For example `kubectl-anthos-config.yaml`.

  ### macOS

  ```
  mkdir -p  $HOME/Library/Preferences/google/anthos/
  cp [AUTH_CONFIG_FILE] $HOME/Library/Preferences/google/anthos/kubectl-anthos-config.yaml
  ```

  where <var translate="no">\[AUTH_CONFIG_FILE\]</var> is the name of your authentication
  configuration file. For example `kubectl-anthos-config.yaml`.

  ### Windows

  ```
  md "%APPDATA%\google\anthos"
  copy [AUTH_CONFIG_FILE] "%APPDATA%\google\anthos\kubectl-anthos-config.yaml"
  ```

  where <var translate="no">\[AUTH_CONFIG_FILE\]</var> is the name of your authentication
  configuration file. For example `kubectl-anthos-config.yaml`.
- Using your internal tools to push the authentication configuration file onto
  each user's machine. For example, you could use your tooling to push files
  using the default `kubectl-anthos-config.yaml` filename into their default
  locations on each user's machine:

  ### Linux

  ```
  $HOME/.config/google/anthos/kubectl-anthos-config.yaml
  ```

  ### macOS

  ```
  $HOME/Library/Preferences/google/anthos/kubectl-anthos-config.yaml
  ```

  ### Windows

  ```
  %APPDATA%\google\anthos\kubectl-anthos-config.yaml
  ```

### Custom configuration

The gcloud CLI expects the authentication configuration file to be stored in
the default location and with the default filename `kubectl-anthos-config.yaml`
as mentioned in the prior section. However, you have the option to rename or
store your authentication configuration file in an alternate location. If the
file's name and location differ from the default, you must append the
`--login-config` flag to each command that you run when you authenticate with
the cluster. The extra command flag passes in the custom path and filename.
To learn more about the command flag, see
[Authenticating through the gcloud CLI](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#plugin_to_authenticate).

## Obtaining the authentication configuration file

This section is for [developers](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#personas).

Your administrator is responsible for creating your authentication configuration
file and then providing it to you. For more details, see
[Distributing the authentication configuration file](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#auth_config_loc).

By default, the gcloud CLI uses a default filename and storage location for
your authentication configuration file. If you were manually provided the file
and need to save it on your machine, use the defaults to simplify your
[`gcloud` authentication](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#plugin_to_authenticate) commands.

Use the following commands to copy the authentication configuration file to the
default location:

### Linux

```
mkdir -p  $HOME/.config/google/anthos/
cp [AUTH_CONFIG_FILE] $HOME/.config/google/anthos/kubectl-anthos-config.yaml
```

where <var translate="no">\[AUTH_CONFIG_FILE\]</var> is the name of your authentication
configuration file. For example `kubectl-anthos-config.yaml`.

### macOS

```
mkdir -p  $HOME/Library/Preferences/google/anthos/
cp [AUTH_CONFIG_FILE] $HOME/Library/Preferences/google/anthos/kubectl-anthos-config.yaml
```

where <var translate="no">\[AUTH_CONFIG_FILE\]</var> is the name of your authentication
configuration file. For example `kubectl-anthos-config.yaml`.

### Windows

```
md "%APPDATA%\google\anthos"
copy [AUTH_CONFIG_FILE] "%APPDATA%\google\anthos\kubectl-anthos-config.yaml"
```

where <var translate="no">\[AUTH_CONFIG_FILE\]</var> is the name of your authentication
configuration file. For example `kubectl-anthos-config.yaml`.

If you choose to use a different filename or location, you have the option to
include the `--login-config` flag with each of your authentication requests.
See the following section for details about using the `gcloud anthos auth login`
command.

## Authenticating with clusters

This section is for [developers](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#personas).

Now that gcloud CLI is installed on your machine and the
authentication configuration file has been provided to you by your
administrator, you can use either the gcloud CLI or
the Google Cloud console to authenticate with your clusters.

### Authenticating through the gcloud CLI

Run `gcloud` commands to authenticate with your clusters:

1. Run the `gcloud anthos auth login` command to initiate the authentication
   flow:

   ```
   gcloud anthos auth login \
    --cluster [CLUSTER_NAME] \
    --user [USER_NAME] \
    --login-config [AUTH_CONFIG_FILE_PATH] \
    --login-config-cert [CA_CERT_PEM_FILE] \
    --kubeconfig [CLUSTER_KUBECONFIG]
   ```

   where:
   - <var translate="no">\[CLUSTER_NAME\]</var> (optional) specifies the name of your
     cluster. If this flag is omitted, you are prompted to choose from the
     clusters that are specified in your authentication configuration file.

   - <var translate="no">\[USER_NAME\]</var> (optional) specifies the username for
     the credentials stored in the `kubeconfig` file. The default value is
     `[CLUSTER_NAME]-anthos-default-user`.

   - <var translate="no">\[AUTH_CONFIG_FILE_PATH\]</var> (optional) specifies the custom path or
     URL to where your authentication configuration file is stored or hosted.
     You can omit this parameter, if the file is in the
     [default](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.6/installing/oidc-google.md.txt#auth_config_loc) location.
     Example: `--login-config /path/to/custom/authentication-config.yaml`

   - <var translate="no">\[CA_CERT_PEM_FILE\]</var> (optional) specifies the path to a PEM
     certificate file from your CA. If your authentication configuration file
     is hosted securely, you can use an HTTPS connection to access the file.
     Example: `--login-config-cert my-cert.pem`

   - <var translate="no">\[CLUSTER_KUBECONFIG\]</var> (optional) specifies the custom path
     to your cluster's `kubeconfig` file. The OIDC ID tokens that are
     returned by your OpenID provider are stored in the `kubeconfig` file.

     Use this flag if your `kubeconfig` file resides in a location other than
     the
     [default](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig).
     If this flag is omitted, a new `kubeconfig` file is created in the default
     location. Example: `--kubeconfig /path/to/custom.kubeconfig`

   **Examples**:
   - Authenticate to specific cluster:

         gcloud anthos auth login --cluster my-production-cluster

   - Use a prompt to select which cluster to authenticate with:

         gcloud anthos auth login

     Result:

         Please use the --cluster flag to specify a cluster from the list below:
         Source: $HOME/.config/google/anthos/kubectl-anthos-config.yaml
         1. Cluster: test-cluster ServerIP: https://192.168.0.1:6443
         2. Cluster: test-cluster-2 ServerIP: https://192.168.0.2:6443
         3. Cluster: my-production-cluster ServerIP: https://192.168.0.3:6443

   - Use a hosted authentication configuration file:

         gcloud anthos auth login \
          --cluster my-production-cluster \
          --login-config HTTPS://my-secure-server/kubectl-anthos-config.yaml \
          --login-config-cert my-cert.pem

2. Enter your credentials in the browser-based consent screen that opens.

3. Verify that authentication was successful by running one of the
   `kubectl` commands to retrieve details about your cluster. For
   example:

   ```
   kubectl get nodes --kubeconfig [CLUSTER_KUBECONFIG]
   ```

Result: Your `kubeconfig` file now contains an ID token that your `kubectl`
commands will use to authenticate with the Kubernetes API server on your
cluster.

### Using SSH to authenticate from a remote machine

Suppose you want to SSH into a remote machine and authenticate to a cluster
from the remote machine. To do this, your authentication configuration file must
be on the remote machine, and you must be able to reach your Open ID provider
from your local machine.

On your local machine, run the following command:

```
ssh [USER_NAME]@[REMOTE_MACHINE] -L [LOCAL_PORT]:localhost:[REMOTE_PORT]
```

where:

- <var translate="no">\[USER_NAME\]</var> and <var translate="no">\[REMOTE_MACHINE\]</var> are the standard
  values used to log in with SSH.

- <var translate="no">\[LOCAL_PORT\]</var> is an open port of your choice on your local machine
  that you will use to access the remote machine.

- <var translate="no">\[REMOTE_PORT\]</var> is the port you configured for your OIDC redirect
  URL. You can find this in the `kubectlRedirectURI` field of your
  authentication configuration file.

In your SSH shell, run the following command to initiate authentication:

```
gcloud anthos auth login --login-config [AUTH_CONFIG_FILE]
```

where <var translate="no">\[AUTH_CONFIG_FILE\]</var> is the path of your
authentication configuration file on the remote machine.

On your local machine, in a browser, go to
http://localhost:<var class="edit" translate="no">\[LOCAL_PORT\]</var>/login and complete the
OIDC login flow.

Now the kubeconfig file on your remote machine has the token that you need to
access the cluster.

In your SSH shell, verify that you have access to the cluster:

```
kubectl --kubeconfig [CLUSTER_KUBECONFIG] get nodes
```

### Authenticating through the Google Cloud console

Initiate the authentication flow from the Kubernetes clusters page in the
Google Cloud console:

1. Open the Google Cloud console:

   [Visit the Kubernetes clusters page](https://console.cloud.google.com/kubernetes/list)
2. Locate your Google Distributed Cloud cluster in the list and then click
   **Login**.

3. Select **Authenticate with the Identity Provider configured for the
   cluster** , and then click **LOGIN**.

   You are redirected to your identity provider, where you might need to
   log in or consent to Google Cloud console accessing your account. Then you
   are redirected back to the **Kubernetes clusters** page in
   Google Cloud console.

## Troubleshooting your OIDC configuration

Review the following behaviors and errors to help resolve your OIDC issues:

Invalid configuration
:   If Google Cloud console cannot read the OIDC configuration from your
    cluster, the **LOGIN** button will be disabled.

Invalid provider configuration
:   If your identity provider configuration is invalid, you will see an error
    screen from your identity provider after you click **LOGIN**.
    Follow the provider-specific instructions to correctly configure the provider or
    your cluster.

Invalid permissions
:   If you complete the authentication flow, but still don't see the details of
    the cluster, make sure you granted the correct RBAC permissions to the account
    that you used with OIDC. Note that this might be a different account from the
    one you use to access Google Cloud console.

`Error: missing 'RefreshToken' field in 'OAuth2Token' in credentials struct`
:   You might get this error if the authorization server prompts for consent, but
    the required authentication parameter wasn't provided. Provide the
    `prompt=consent` parameter to Google Distributed Cloud configuration
    file's `oidc: extraparams` field, and regenerate the client
    authentication file with the `--extra-params prompt=consent` flag.

## What's next

- Learn more about [scopes and claims](https://developer.okta.com/blog/2017/07/25/oidc-primer-part-1#key-concepts-scopes-claims-and-response-types).