Skip to Content
PlatformMaintainAccessNon human

Set up keyless authentication with GCP

Prerequisites

  • Sufficient GCP privileges to create and manage service accounts

  • Editor or Owner privileges in the Mondoo space, organization, or platform to which your workload needs access

Step A: Prepare your GCP environment for WIF

  1. Create a GCP service account. To learn how, read Create service accounts.

  2. Go the Service account details page and note the service account's unique ID. You need this value when you configure the workload identity provider.

  3. Assign the managed identity to a virtual machine or another resource where your workload runs. To learn how, read Create a VM and attach the service account.

Step B: Create a new workload identity provider in Mondoo

  1. In the Mondoo App, navigate to the space or organization in which you want to set up keyless access for non-human users.

  2. In the left navigation, select Settings, then Workload Identity.

    The Workload Identity settings page in the Mondoo App, listing workload identity providers with their expiration, created, and last used times

  3. Select ADD PROVIDER, then select Google.

  4. In the Issuer URL box, keep the default https://accounts.google.com.

  5. In the Subject box, enter the unique ID of the GCP service account you created in Step A.

  6. In the Expiration time list, choose how long sessions authenticated with this WIF provider last: 30, 45, or 60 minutes.

  7. In the Name and Description boxes, provide a short name and longer description that help you and your teammates recognize the source and purpose of the provider.

  8. In the Roles list, check the roles the workload needs. Agent is selected by default. To learn what each role allows, read What roles can you assign?.

  9. Select ADD PROVIDER.

    The Add Google workload identity provider form in the Mondoo App, with issuer URL, subject, expiration time, name, description, and roles

    Mondoo generates and displays the configuration values that you need to give your workload access. Copy them, then select Finalize setup.

Step C: Exchange your token for access

Fetch the local token:

curl -H "Metadata-Flavor: Google" "http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/identity?audience=test"

Make a curl call to exchange a local token for a short-lived Mondoo service account:

curl --request POST \
  --url 'UNIVERSE_DOMAIN/SecureTokenService/ExchangeExternalToken?=' \
  --header 'content-type: application/json' \
  --data '{
  "audience": "AUDIENCE",
  "issuer_uri": "ISSUER",
  "jwt_token": "TOKEN"
  }'
For...Substitute...
AUDIENCEThe audience value Mondoo provided when you followed the instructions in Step B above
ISSUERThe issuer value Mondoo provided when you followed the instructions in Step B above
TOKENThe token fetched using the curl command above

This call returns a Mondoo service account in the form of a base64_credential value, which your workload can use to access Mondoo by setting MONDOO_CONFIG_BASE64 to the returned value.

On this page