Skip to content

Apps Script Service Account Impersonation

Published on Markdown

Unlike many other environments in Google Cloud that provide default application credentials, Apps Script is built on OAuth and user credentials. However there are many cases, where a service account is needed to access Google Cloud resources. For example, a service account is needed to interact with the Google Chat API as a Chat App.

Instead of downloading the service account key and storing it in the Apps Script project, the service account can be impersonated using the ScriptApp.getOAuthToken() and user as principal. This allows the service account to be used without downloading the key.

Setup service account impersonation and Apps Script

There a few steps to get this working right in Apps Script:

  1. Create a service account in the Google Cloud project
  2. Grant the principal (your account or whoever executes the script) access to the service account
  3. Add the Service Account Token Creator role to the principal (Owner role is not sufficient)
  4. Enable the IAM Service Account Credentials API in the Google Cloud project
  5. Add the Google Cloud project number to the Apps Script project settings
  6. Add the following scopes to the Apps Script project manifest:
JSON
{
  "oauthScopes": [
    "https://www.googleapis.com/auth/script.external_request",
    "https://www.googleapis.com/auth/cloud-platform"
  ]
}

A more detailed explanation of these steps can be found in the Create short-lived credentials for a service account.

IAM Service Account Credentials API and impersonation

To generate the an access token for the service account, the generateAccessToken endpoint of the IAM Credentials API is used. Calling this endpoint requires code similar to the following using UrlFetchApp and ScriptApp.getOAuthToken():

JavaScript
/**
 * Generates an access token using impersonation. Requires the following:
 *
 * - Service Account Token Creator
 * - IAM Credentials API
 *
 * @params {string} serviceAccountEmail
 * @params {Array<string>} scope
 * @params {string} [lifetime="3600s"]
 * @returns {string}
 */
function generateAccessTokenForServiceAccount(
  serviceAccountEmailOrId,
  scope,
  lifetime = "3600s", // default
) {
  const host = "https://iamcredentials.googleapis.com";
  const url = `${host}/v1/projects/-/serviceAccounts/${serviceAccountEmailOrId}:generateAccessToken`;

  const payload = {
    scope,
    lifetime,
  };

  const options = {
    method: "POST",
    headers: { Authorization: "Bearer " + ScriptApp.getOAuthToken() },
    contentType: "application/json",
    muteHttpExceptions: true,
    payload: JSON.stringify(payload),
  };

  const response = UrlFetchApp.fetch(url, options);

  if (response.getResponseCode() < 300) {
    return JSON.parse(response.getContentText()).accessToken;
  } else {
    throw new Error(response.getContentText());
  }
}

This function can be used to generate an access token for the service account. The access token can then be used to make requests to Google Cloud APIs.

Generating and using service account access tokens in Apps Script

Now I can use this function to generate an access token for the service account and verify it contains valid scopes:

JavaScript
JavaScript
function main() {
  const token = generateAccessTokenForServiceAccount(
    // can also be the email: [email protected]
    "112304111718889638064",
    ["https://www.googleapis.com/auth/datastore"],
  );

  // verify the token
  console.log(
    UrlFetchApp.fetch(
      `https://www.googleapis.com/oauth2/v1/tokeninfo?access_token=${token}`,
    ).getContentText(),
  );
}

The output looks like the following:

GNU Bash
GNU Bash
12:53:12 PM	Notice	Execution started
12:53:13 PM	Info	ya29.c.c0AY_VpZ... // truncated
12:53:13 PM	Info	{
  "issued_to": "112304111718889638064",
  "audience": "112304111718889638064",
  "scope": "https://www.googleapis.com/auth/datastore",
  "expires_in": 3599,
  "access_type": "online"
}
12:53:14 PM	Notice	Execution completed

To use this token to make requests to Google Cloud APIs, the token can be added to the Authorization header of the request instead of the ScriptApp.getOAuthToken() user token:

const options = {
  headers: { Authorization: `Bearer ${token}` },
};

UrlFetchApp.fetch(url, options);

Be sure to update the scopes in the generateAccessTokenForServiceAccount function to match the scopes needed for the request.

Frequently Asked Questions

What is service account impersonation in Apps Script?

Service account impersonation in Apps Script is a technique that allows you to use a service account to access Google Cloud resources without downloading and storing the service account's private key. Instead, you use the user's credentials to generate a short-lived access token for the service account.

Why should I use service account impersonation instead of downloading a service account key?

Downloading and storing a service account key is a security risk. If the key is compromised, it can be used to access your Google Cloud resources. Service account impersonation is a more secure method because it uses short-lived access tokens and avoids the need to manage private keys.

How do I set up service account impersonation in Apps Script?

To set up service account impersonation, you need to create a service account, grant the user running the script the "Service Account Token Creator" role, enable the IAM Service Account Credentials API, and add the necessary OAuth scopes to your Apps Script project.

How do I generate an access token for a service account in Apps Script?

You can generate an access token by calling the generateAccessToken endpoint of the IAM Credentials API using UrlFetchApp. You'll need to pass the service account's email address and the desired scopes in the request body, and use the user's OAuth token for authentication.

How do I use the generated service account access token?

Once you have the access token, you can use it to make requests to Google Cloud APIs by adding it to the Authorization header of your UrlFetchApp requests in the format Bearer <token>.

Disclaimer: I am a member of the Google Workspace Developer Relations team. The opinions expressed here are my own and do not necessarily represent those of Google.

© 2024 by Justin Poehnelt is licensed under CC BY-SA 4.0