Set up OAuth for Cloud IAP

Creating an OAuth client for Cloud IAP on Google Cloud Platform (GCP)

If you want to use Cloud Identity-Aware Proxy (Cloud IAP) when deploying Kubeflow on GCP, then you must follow these instructions to create an OAuth client for use with Kubeflow.

You can skip the instructons on this page if you want to use basic authentication (username and password) with Kubeflow instead of Cloud IAP. Cloud IAP is recommended for production deployments or deployments with access to sensitive data.

Follow the steps below to create an OAuth client ID that identifies Cloud IAP when requesting access to a user’s email account. Kubeflow uses the email address to verify the user’s identity.

  1. Set up your OAuth consent screen:

    • In the Application name box, enter the name of your application. The example below uses the name “Kubeflow”.
    • Under Support email, select the email address that you want to display as a public contact. You must use either your email address or a Google Group that you own.
    • If you see Authorized domains, enter

      • where <project> is your Google Cloud Platform (GCP) project ID.
      • If you are using your own domain, such as, you should add that as well
      • The Authorized domains option appears only for certain project configurations. If you don’t see the option, then there’s nothing you need to set.
    • Click Save.

    • Here’s an example of the completed form:
      OAuth consent screen

  2. On the credentials tab:

    • Click Create credentials, and then click OAuth client ID.
    • Under Application type, select Web application.
    • In the Name box enter any name for your OAuth client ID. This is not the name of your application nor the name of your Kubeflow deployment. It’s just a way to help you identify the OAuth client ID.
    • In the Authorized redirect URIs box, enter the following (if it’s not already present in the list of authorized redirect URIs):<CLIENT_ID>:handleRedirect
      • <CLIENT_ID> is the OAuth client ID, something like
      • Note that the URI is not dependent on the Kubeflow deployment or endpoint. Multiple Kubeflow deployments can share the same OAuth client without the need to modify the redirect URIs.
    • Here’s an example of the completed form: OAuth credentials

  3. Press Enter/Return to add the URI. Check that the URI now appears as a confirmed item under Authorized redirect URIs. (The URI should no longer be editable.)

  4. Make note of the client ID and client secret that appear in the OAuth client window. You need them later to enable Cloud IAP.

Next steps

Choose one of the following ways to deploy Kubeflow:

  • Using the UI. This option provides a simple way to deploy Kubeflow.
  • Using the CLI. This option provides more control over the deployment process.