Service Account Credentials API

Related topics

• service account impersonation depends on Service Account Credentials API From the official documentation: “To impersonate a service account, you need to enable the Service Account Credentials API in your project.”
• Data Access audit logs configures Service Account Credentials API From the official documentation: “Enabling Data Access audit logs for the IAM API also enables these audit logs for the Service Account Credentials API.”
• Service Account Credentials API works with short-lived credentials From the official documentation: “[Create short-lived credentials](/iam/docs/create-short-lived-credentials-direct) using the Service Account Credentials API, then use those credentials to authenticate an API request.”
• 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 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 an alternative to short-lived credentials From the official documentation: “Short-lived service account credentials are useful for scenarios where you need to grant limited access to resources for trusted service accounts, and they reduce the risk compared to using long-lived credentials like service account keys.”
• Service account keys is an alternative to short-lived credentials From the official documentation: “Applications can obtain short-lived credentials or, less securely, use service account keys to authenticate.”