1. Docs
  2. Pulumi Cloud
  3. OpenID
  4. OpenID Provider
  5. Google Cloud

Configuring OpenID Connect for Google Cloud

    This document outlines the steps required to configure Pulumi to use OpenID Connect to authenticate with Google Cloud. OIDC in Google Cloud uses workload identity federation to allow access to resources. Access to the resources is authorized using attribute conditions that validate the contents of the OIDC token issued by the Pulumi Cloud.

    Prerequisites

    Please note that this guide provides step-by-step instructions based on the official provider documentation which is subject to change. For the most current and precise information, always refer to the official Google Cloud documentation.

    Create a Workload Identity Pool and Provider

    1. Navigate to the Workload Identity Pools page in the Google Cloud console.
    2. Select your Google Cloud project.
    3. Click the Create Pool button.
    4. Provide a name and an optional description. then click Continue
    5. In the Add a provider to pool dropdown, select OpenID Connect (OIDC).
    6. Provide a name for the provider.
    7. In the Issuer field, enter https://api.pulumi.com/oidc.
    8. In the Audiences section, select the Allowed audiences radio button. Provide the name of your Pulumi organization as the value, then click Continue.
    9. In the Configure provider attributes section, provide the value of assertion.sub in the OIDC 1 field. Then click Save.

    Configure a Service Account

    Once you have created your workload identity pool and provider, you will be directed to the pool details page. If you already have an appropriate service account created, skip ahead to the steps found in the Grant access to the service account section. Otherwise, continue through the steps below to create a new one.

    Create a new service account

    1. Navigate to the Service Accounts page.
    2. Select your Google Cloud project.
    3. Click “Create Service Account”.
    4. Enter a value for the Service account name field. Then click Create And Continue
      • The Service account ID field will auto-populate based on this value.
    5. In the Grant this service account access to project section, select the role(s) that provides the relevant access to your Pulumi service. Then click Continue.
    6. Leave the values in the next section blank and click Done.

    Grant access to the service account

    1. In your workload identity pool’s details page, click the Grant Access button.
    2. In the Select service account dropdown, select the desired service account to associate with the pool.
    3. Under the Select principals section, click the Only identities matching the filter radio button.
    4. In the Attribute name dropdown, select Subject.
    5. In the Attribute value field, provide a valid subject claim (see examples at the end of this section). Then click Save.

    Make a note of the project ID, workload identity pool ID, provider ID, and service account email address from the previous steps. These will be necessary to enable OIDC for your service.

    Subject claim examples

    Depending on the Pulumi service you are configuring OIDC for, the value of the subject claim will be different. You can learn more about configuring OIDC with Pulumi by referring to the relevant documentation.

    The below sections show examples that correspond to each OIDC-supported service.

    Pulumi Deployments

    To enable valid operations on a specific stack, Google federated credentials require an exact match on the OIDC token subject claim. Unfortunately, the subject identifier does not currently allow wildcards. Therefore, you must create credentials for each permutation of the subject claim that is possible for the stack.

    For example, to enable all of the valid operations on a stack named dev of the core project in the contoso organization, you would need to create credentials for each of the following subject identifiers:

    • pulumi:deploy:org:contoso:project:core:stack:dev:operation:preview:scope:write
    • pulumi:deploy:org:contoso:project:core:stack:dev:operation:update:scope:write
    • pulumi:deploy:org:contoso:project:core:stack:dev:operation:refresh:scope:write
    • pulumi:deploy:org:contoso:project:core:stack:dev:operation:destroy:scope:write

    Pulumi ESC

    The below is an example of a valid subject claim for the development environment of the contoso organization:

    • pulumi:environments:org:contoso:env:development

    You can learn more about setting up OIDC for Pulumi ESC by referring to the relevant Pulumi documentation.

    If you are integrating Pulumi ESC with Pulumi IaC, the default subject identifier of the ESC environment will not work at this time. There is a known issue with the subject identifier’s value sent to Azure from Pulumi.

    Use ‘subjectAttributes’ to customize the subject identifier to work with Pulumi IaC. Alternatively, you can use this syntax: pulumi:environments:org:contoso:env:<yaml> when configuring the subject claim in your cloud provider account. Make sure to replace contoso with the name of your Pulumi organization and use the literal value of <yaml> as shown.

    Subject customization

    It is possible to customize the OIDC token subject claim by setting configuring the subjectAttributes setting. It expects an array of keys to include in it:

    • rootEnvironment.name: the name of the root evironment being evaluated
    • currentEnvironment.name: the name of the current environment being evaluated
    • pulumi.user.login: the login identifier of the user opening the environment
    • pulumi.organization.login: the login identifier of the organization

    The subject always contains the following prefix pulumi:environments:pulumi.organization.login:{ORGANIZATION_NAME} and every key configured will be appended to this prefix. For example, consider the following environment:

    values:
      gcp:
        login:
          fn::open::gcp-login:
            oidc:
              ...
              subjectAttributes:
                - currentEnvironment.name
                - pulumi.user.login
    

    The subject will be pulumi:environments:pulumi.organization.login:contoso:currentEnvironment.name:development:pulumi.user.login:userLogin. Note how the keys and values are appended along with the prefix.

    Configure OIDC in the Pulumi Console

    Pulumi Deployments

    In addition to the Pulumi Console, deployment settings including OIDC can be configured for a stack using the pulumiservice.DeploymentSettings resource or via the REST API.
    1. Navigate to your stack in the Pulumi Console.
    2. Open the stack’s “Settings” tab.
    3. Choose the “Deploy” panel.
    4. Under the “OpenID Connect” header, toggle “Enable Google Cloud Integration”.
    5. Enter the numerical ID of your Google Cloud project in the “Project ID” field.
    6. Enter the workload pool ID, identity provider ID, and service account email address in the “Workload Pool ID”, “Identity Provider ID”, and “Service Account Email Address” fields.
    7. If desired, enter the stack’s Google Cloud region in the “Region” field. This is typically unnecessary.
    8. If you would like to constrain the duration of the temporary Google Cloud credentials, enter a duration in the form “XhYmZs” in the “Session Duration” field.
    9. Click the “Save deployment configuration” button.

    With this configuration, each deployment of this stack will attempt to exchange the deployment’s OIDC token for Google Cloud credentials using the specified federated identity prior to running any pre-commands or Pulumi operations. The fetched credentials are published as a credential configuration in the GOOGLE_CREDENTIALS environment variable. The raw OIDC token is also available for advanced scenarios in the PULUMI_OIDC_TOKEN environment variable and the /mnt/pulumi/pulumi.oidc file.

    Pulumi ESC

    To configure OIDC for Pulumi ESC, create a new environment in the Pulumi Console. Make sure that you have the correct organization selected in the left-hand navigation menu. Then:

    1. Click the Environments link.

    2. Click the Create environment button.

    3. Provide a name for your environment.

      • This should be the same as the name provided in the subject claim in the previous steps.
    4. Click the Create environment button.

    5. You will be presented with a split-pane editor view. Delete the default placeholder content in the editor and replace it with the following code:

      values:
        gcp:
          login:
            fn::open::gcp-login:
              project: <your-project-id>
              oidc:
                workloadPoolId: <your-pool-id>
                providerId: <your-provider-id>
                serviceAccount: <your-service-account>
        environmentVariables:
          GOOGLE_PROJECT: ${gcp.login.project}
          CLOUDSDK_AUTH_ACCESS_TOKEN: ${gcp.login.accessToken}
        pulumiConfig:
          gcp:accessToken: ${gcp.login.accessToken}
      
    6. Replace <your-project-id>, <your-pool-id>, <your-provider-id>, and <your-service-account> with the values from the previous steps.

    7. Scroll to the bottom of the page and click Save.

    You can validate that your configuration is working by running either of the following:

    • esc open <your-org>/<your-environment> command of the ESC CLI
    • pulumi env open <your-org>/<your-environment> command of the Pulumi CLI

    Make sure to replace <your-org> and <your-environment> with the values of your Pulumi organization and environment file respectively. You should see output similar to the following:

    {
      "environmentVariables": {
        "GOOGLE_PROJECT": 111111111111
        "CLOUDSDK_AUTH_ACCESS_TOKEN": "ya29...."
      },
      "gcp": {
        "login": {
          "accessToken": "ya29.....",
          "expiry": "2023-11-09T11:12:41Z",
          "project": 111111111111,
          "tokenType": "Bearer"
        }
      },
      "pulumiConfig": {
        "gcp:accessToken": "ya29...."
      }
    }
    

    To learn more about how to set up and use the various providers in Pulumi ESC, please refer to the relevant Pulumi documentation.

    Automate OIDC Configuration

    Our Examples repository provides a wide variety of example automations using Pulumi Infrastructure as Code (IaC). If you want to automate the configuration and deployment of OIDC between Pulumi and GCP, take a look at the following examples to help you get started:

      Introducing Pulumi Copilot - Intelligent Cloud Management