Service Account Token Creator

Related topics

• service account impersonation depends on Service Account Token Creator From the official documentation: “You must have the Service Account Token Creator (`roles/iam.serviceAccountTokenCreator`) IAM role on the service account you are impersonating.”
• Service Account Token Creator configures service account impersonation From the official documentation: “Paste the unique email address into the **New principals** field and assign the **Service Account Token Creator** role (`roles/iam.serviceAccountTokenCreator`).”
• Service Account Token Creator configures service accounts From the official documentation: “Grant the **Service Account Token Creator** role to the service account.”
• service agent depends on Service Account Token Creator From the official documentation: “To enable the service agent to generate an [access token](/docs/authentication/token-types#access-tokens) from the user-managed service account, grant the service agent access to the user-managed service account, and assign the **Service Account Token Creator** role…”
• service account key is part of service account From the official documentation: “A service account can have up to 10 keys.”
• service account impersonation is an alternative to service account key From the official documentation: “If you cannot use a user account or service account impersonation for local development, you can use a service account key.”
• service account keys is part of service account From the official documentation: “You use the Identity and Access Management API to create a new key pair for a service account.”
• service account impersonation depends on service account From the official documentation: “Service account impersonation should always involve two principals: a principal that represents the caller, and the service account that is being impersonated, called the privilege-bearing service account.”
• service account impersonation is an alternative to service account keys From the official documentation: “If you use impersonation, instead of creating service account keys that anyone can use to access your deployment, you manage access by granting or revoking the [Service Account Token Creator (`roles/iam.serviceAccountTokenCreator`) IAM…”
• service account key is part of service accounts From the official documentation: “Managing service identities involves both the service identity (represented by a `ProjectServiceAccount` resource) and its associated credentials (public and private key pairs).”
• service account keys depends on service accounts From the official documentation: “A [service account key](/iam/docs/service-account-overview) lets you authenticate a request as a service account.”
• service agent is part of service account From the official documentation: “Service accounts can be divided into *user-managed service accounts* and Google-managed service accounts, which are called *service agents*:”