如需使用 Google Cloud，用户和工作负载需要一个Google Cloud 可以识别的身份。
本页概述了可用于配置用户身份和工作负载身份的方法。
用户身份
您可以通过多种方式配置用户身份，以便 Google Cloud能够识别这些身份：
创建 Cloud Identity 或 Google Workspace 账号：拥有 Cloud Identity 或 Google Workspace 账号的用户可以向 Google Cloud 进行身份验证并获准使用 Google Cloud 资源。Cloud Identity 和 Google Workspace 账号是指由您的组织管理的用户账号。
设置以下联合身份策略之一：
使用 Cloud Identity 或 Google Workspace 进行联合：将外部身份与相应的 Cloud Identity 或 Google Workspace 账号同步，以便用户可以使用其外部凭据登录 Google 服务。使用此方法时，用户需要两个账号：一个外部账号和一个 Cloud Identity 或 Google Workspace 账号。您可以使用 Google Cloud Directory Sync (GCDS) 等工具将这些账号保持同步。
员工身份联合：使用您的外部身份提供方 (IdP) 让用户登录 Google Cloud 并访问Google Cloud 资源和产品。使用员工身份联合时，用户只需要一个账号：其外部账号。此类用户身份有时也称为“联合身份”。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-01。"],[[["\u003cp\u003eGoogle Cloud requires users and workloads to have a recognizable identity for access.\u003c/p\u003e\n"],["\u003cp\u003eUser identities can be established through Cloud Identity/Google Workspace accounts or by setting up federated identity strategies.\u003c/p\u003e\n"],["\u003cp\u003eWorkload identities on Google Cloud can use Workload Identity Federation, Google Cloud service accounts, or managed workload identities.\u003c/p\u003e\n"],["\u003cp\u003eWorkload identities for workloads outside of Google Cloud can leverage Workload Identity Federation or service account keys, with the latter carrying security risks.\u003c/p\u003e\n"],["\u003cp\u003eThe method to choose to configure a workload identity depends on where the workloads are running, in or out of Google cloud.\u003c/p\u003e\n"]]],[],null,["# Identity management for Google Cloud\n\nTo use Google Cloud, users and workloads need an identity that\nGoogle Cloud can recognize.\n\nThis page outlines the methods that you can use to configure identities for\nusers and workloads.\n\nUser identities\n---------------\n\nThere are several ways to configure user identities so that Google Cloud\ncan recognize them:\n\n- **Create Cloud Identity or Google Workspace accounts**: Users with Cloud Identity or Google Workspace accounts can authenticate to Google Cloud and be authorized to use Google Cloud resources. Cloud Identity and Google Workspace accounts are user accounts that are managed by your organization.\n\n| **Note:** Google Workspace accounts may have one or more *[alternate email addresses (email alias)](https://support.google.com/a/answer/33327)* . If you grant a role to a principal's *email alias* , the role is granted to the *primary email* instead. It's not possible to grant a role to only the *email alias*.\n| **Warning:** Granting a role to a principal's *email alias* reveals the *primary email*.\n\n- **Set up one of the following federated identity strategies**:\n\n - **Federation using Cloud Identity or Google Workspace** : Sync external identities with corresponding Cloud Identity or Google Workspace accounts so that users can sign in to Google services with their external credentials. With this method, users need two accounts: an external account, and a Cloud Identity or Google Workspace account. You can keep these accounts synchronized using a tool like [Google Cloud Directory Sync\n (GCDS)](https://tools.google.com/dlpage/dirsync/).\n - **Workforce Identity Federation** : Use your external identity provider (IdP) to sign in your users to Google Cloud and let them access Google Cloud resources and products. With Workforce Identity Federation, users need only one account: their external account. This type of user identity is sometimes referred to as a *federated identity*.\n\nTo learn more about these methods for setting up user identities, see\n[User identities overview](/iam/docs/user-identities).\n\nWorkload identities\n-------------------\n\nGoogle Cloud provides the following types of identity services for workloads:\n\n- [**Workload Identity Federation**](/iam/docs/workload-identity-federation)\n lets your workloads access most Google Cloud services by using an\n identity that is provided by an IdP. Workloads that use\n Workload Identity Federation can run on Google Cloud,\n Google Kubernetes Engine (GKE), or other platforms, such as AWS, Azure, and\n GitHub.\n\n- [**Google Cloud service accounts**](/iam/docs/service-account-overview) can act as\n identities for workloads. Instead of granting access to a workload directly,\n you grant access to a service account, then let the workload use the service\n account as its identity.\n\n- [**Managed workload identities**](/iam/docs/managed-workload-identity) [**(Preview)**](/products#product-launch-stages)\n let you bind strongly attested identities to your Compute Engine\n workloads. You can use managed workload identities to authenticate your\n workloads to other workloads using [mutual TLS (mTLS)](https://en.wikipedia.org/wiki/Mutual_authentication),\n but they cannot be used for authenticating to Google Cloud APIs.\n\nThe methods that you can use depend on where your workloads are running.\n\nIf you're running workloads on Google Cloud, you can use the following\nmethods to configure workload identities:\n\n- **Workload Identity Federation for GKE**: Grant IAM access to\n GKE clusters and Kubernetes service accounts. Doing so lets the\n clusters' workloads access most Google Cloud services directly, without\n using IAM service account impersonation.\n\n- **Attached service accounts**: Attach a service account to a resource so that\n the service account acts as the resource's default identity. Any workloads\n running on the resource use the service account's identity when accessing\n Google Cloud services.\n\n- **Short-lived service account credentials**: Generate and use short-lived\n service account credentials whenever your resources need to access to\n Google Cloud services. The most common types of credentials are\n OAuth 2.0 access tokens and OpenID Connect (OIDC) ID tokens.\n\nIf you're running workloads outside of Google Cloud, you can use the\nfollowing methods to configure workload identities:\n\n- **Workload Identity Federation**: Use credentials from external identity providers to generate short-lived credentials, which workloads can use to temporarily impersonate service accounts. Workloads can then access Google Cloud resources, using the service account as their identity.\n- **Service account keys**: Use the private portion of a service account's\n public/private RSA key pair to authenticate as the service account.\n\n | **Important:** Service account keys are a security risk if not managed correctly. You should [choose a more secure alternative to service account keys](/docs/authentication#auth-decision-tree) whenever possible. If you must authenticate with a service account key, you are responsible for the security of the private key and for other operations described by [Best practices for managing service account keys](/iam/docs/best-practices-for-managing-service-account-keys). If you are prevented from creating a service account key, service account key creation might be disabled for your organization. For more information, see [Managing secure-by-default organization resources](/resource-manager/docs/secure-by-default-organizations).\n |\n |\n | If you acquired the service account key from an external source, you must validate it before use.\n | For more information, see [Security requirements for externally sourced credentials](/docs/authentication/external/externally-sourced-credentials).\n\nTo learn more about these methods for setting up workload identities, see\n[Workload identities overview](/iam/docs/workload-identities)."]]
