credential configuration file

Related topics

• credential configuration file is an alternative to service account key From the official documentation: “This approach uses the credential configuration files in place of the Google service account key files.”
• credential configuration file configures service account impersonation From the official documentation: “Use a [credential configuration file](https://google.aip.dev/auth/4117) to configure an external application to impersonate a service account.”
• credential configuration file depends on Workload Identity Federation From the official documentation: “Use a [credential configuration file](https://google.aip.dev/auth/4117) to configure an external application to impersonate a service account. This option is only available for applications that use [Workload Identity Federation](/iam/docs/workload-identity-federation).”
• credential configuration file configures workload identity pool From the official documentation: “This file defines the following: - Where to obtain external credentials from - Which workload identity pool and provider to use”
• gcloud CLI depends on credential configuration file From the official documentation: “The [Cloud Client Libraries](/apis/docs/cloud-client-libraries) and the gcloud CLI can automatically obtain external credentials and use these credentials to impersonate a service account. To let libraries and tools complete this process, you must provide a credential…”
• Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• service account key is an alternative to Workload Identity Federation From the official documentation: “For hosts outside of Google Cloud, you can provide a service account key or configure Workload Identity Federation (WIF).”
• service account keys is an alternative to Workload Identity Federation From the official documentation: “Where possible, consider using Workload Identity Federation instead of service account keys.”
• workload identity pool provider is part of workload identity pool From the official documentation: “Add the cluster as a workload identity pool provider.”
• service account key is part of service account From the official documentation: “A service account can have up to 10 keys.”
• gcloud CLI works with Workload Identity Federation From the official documentation: “Support for Workload Identity Federation in gcloud CLI is available in [version 363.0.0 and later versions of the gcloud CLI](/sdk/docs/components#updating_components).”
• 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.”
• Application Default Credentials works with service account impersonation From the official documentation: “You can use service account impersonation to set up a local Application Default Credentials (ADC) file.”
• Application Default Credentials works with Workload Identity Federation From the official documentation: “ADC also supports [Workload Identity Federation](#workload-identity-federation), enabling applications to access Google Cloud resources from external platforms like Amazon Web Services (AWS), Microsoft Azure, or any identity provider that supports OpenID Connect (OIDC).”
• gcloud CLI configures Application Default Credentials From the official documentation: “**gcloud CLI**: Manage cloud resources, configure projects, and set up local Application Default Credentials (ADC).”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• Security Token Service works with Workload Identity Federation From the official documentation: “By using Workload Identity Federation, workloads that run on AWS EC2 and Azure VMs can exchange their environment-specific credentials for short-lived Google Cloud Security Token Service tokens.”
• service account impersonation configures Application Default Credentials From the official documentation: “You can use service account impersonation to set up a local ADC file.”
• service account impersonation depends on Security Token Service From the official documentation: “To create a service account for the external workload, do the following: 1. Enable the IAM, Security Token Service, and Service Account Credentials APIs, if any are not already enabled.”
• 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.”
• Workload Identity Federation depends on Security Token Service From the official documentation: “You provide a credential from your identity provider (IdP) to the [Security Token Service](/iam/docs/reference/sts/rest), which verifies the identity on the credential, and then returns a [federated access token](/docs/authentication/token-types#fed-access-tokens) in exchange.”
• Workload Identity Federation depends on workload identity pool From the official documentation: “Using workload identity federation requires a workload identity pool and provider.”
• Workload Identity Federation depends on workload identity pool provider From the official documentation: “Using workload identity federation requires a workload identity pool and provider.”
• Application Default Credentials works with Security Token Service From the official documentation: “The ADC authentication library uses the data in the ConfigMap to exchange the ServiceAccount JWT that you mounted on the Pod for a short-lived [federated access token](/docs/authentication/token-types#fed-access-tokens) from [Security Token…”
• Application Default Credentials depends on service account From the official documentation: “If your `BidiProcessOrder` client runs in a secure environment that can be configured with service account credentials (such as Compute Engine, Google Kubernetes Engine, or your on-premise servers), it can use [Application Default Credentials…”
• Application Default Credentials is an alternative to service account From the official documentation: “There are two ways to obtain credentials for the agent to use: - Let the agent use a service account with private-key authentication - Let the agent use application default credentials (ADC).”
• Application Default Credentials is an alternative to service account keys From the official documentation: “When developers are locally iterating on Terraform configuration, they should authenticate by running [`gcloud auth application-default login`](https://cloud.google.com/sdk/gcloud/reference/auth/application-default/login) to generate application default credentials. Don't…”
• gcloud CLI works with Pub/Sub From the official documentation: “Download and install the [Google Cloud CLI](/sdk/docs/install) to use the gcloud CLI with the Pub/Sub API if you have not installed it previously.”
• gcloud CLI works with Security Token Service From the official documentation: “For headless flows, the gcloud CLI automatically uses the following scope: `https://www.googleapis.com/auth/cloud-platform`. The gcloud CLI then transparently posts your credentials to the Security Token Service endpoint, where it is exchanged for temporary Google Cloud access…”
• service account works with Workload Identity Federation From the official documentation: “[configure Workload Identity Federation](/iam/docs/workload-identity-federation-with-other-clouds) to let applications running on-premises or on other cloud providers use 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 secures Pub/Sub From the official documentation: “The Pub/Sub connection is authenticated using a service account key.”
• Workload Identity Federation configures Pub/Sub From the official documentation: “If your architecture includes an [external identity provider](/iam/docs/workload-identity-federation#providers) such as Active Directory or a local Kubernetes cluster, you can use [workload identity federation](/iam/docs/workload-identity-federation) to manage access to Pub/Sub.”
• Workload Identity Federation depends on service account impersonation From the official documentation: “Workload Identity is the recommended and more secure approach because it uses short-lived, temporary access tokens using service account impersonation, minimizing long-lived secret credential exposure risks.”
• workload identity pool is part of Workload Identity Federation From the official documentation: “This procedure assumes you have already configured Workload Identity Federation for your Google Cloud project, including creating an Identity Pool and Provider, and granting appropriate IAM permissions to your Kubernetes service accounts.”
• workload identity pool depends on Workload Identity Federation From the official documentation: “A workload identity pool is a set of workload identities that is managed by an external IdP and federated by using [Workload Identity Federation](/iam/docs/workload-identity-federation).”