[[["易于理解","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-08-18。"],[[["\u003cp\u003eThis guide outlines the steps to enable access to the Google Cloud Workforce Identity Federation console (federated) through your identity provider (IdP).\u003c/p\u003e\n"],["\u003cp\u003eTo set up, you must first configure Workforce Identity Federation and note your workforce identity pool provider name, which is required to create a redirect URL.\u003c/p\u003e\n"],["\u003cp\u003eYou'll need to create a redirect URL using your workforce identity pool provider name and then configure your IdP with this URL, which can be a Redirect URL or a SAML assertion consumer service (ACS) URL, depending on the protocol.\u003c/p\u003e\n"],["\u003cp\u003eUsers can sign in either by using a custom SSO link that takes them directly to the IdP or by accessing the console (federated) and entering the workforce identity pool provider name.\u003c/p\u003e\n"],["\u003cp\u003eThe console (federated) has limited functionality compared to the Google Cloud console, only providing access to Google Cloud products that support Workforce Identity Federation.\u003c/p\u003e\n"]]],[],null,["# Set up user access to the console (federated)\n\nThis guide shows you how to set up access to the\nGoogle Cloud Workforce Identity Federation console, also known as the console (federated), from your identity provider (IdP) and\nshows you how to provide access instructions to your users.\n\nBefore you begin\n----------------\n\n1. [Configure Workforce Identity Federation](/iam/docs/configuring-workforce-identity-federation)\n in your Google Cloud organization, including a [workforce identity pool](/iam/docs/workforce-identity-federation#workforce-identity-pools) and a [workforce identity pool provider](/iam/docs/workforce-identity-federation#workforce-identity-pool-providers).\n Alternatively, if you use one of the following IdPs, see the IdP-specific\n guides for more information:\n\n - [Configure Microsoft Entra ID-based Workforce Identity Federation](/iam/docs/workforce-sign-in-microsoft-entra-id)\n - [Configure Okta-based Workforce Identity Federation](/iam/docs/workforce-sign-in-okta)\n2. Note your workforce identity pool provider name, which you use later in this\n guide.\n\n| **Note:** For personalization features, such as the user's display name and photo to be displayed correctly, you must configure [attribute mapping](/iam/docs/workforce-identity-federation#attribute-mappings).\n\nSet up redirect URLs in your IdP\n--------------------------------\n\nYou can configure your IdP to post an IdP response and redirect your user to the\nconsole (federated) after your user authenticates. To do this, you must\nconfigure a redirect URL and set it in your IdP\nconfiguration.\n\nTo create the redirect URL, do the following:\n\n1. Share the name of the workforce identity pool provider with your users.\n It is formatted as follows:\n\n locations/global/workforcePools/\u003cvar translate=\"no\"\u003eWORKFORCE_POOL_ID\u003c/var\u003e/providers/\u003cvar translate=\"no\"\u003eWORKFORCE_PROVIDER_ID\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eWORKFORCE_POOL_ID\u003c/var\u003e: the workforce identity pool ID.\n - \u003cvar translate=\"no\"\u003eWORKFORCE_PROVIDER_ID\u003c/var\u003e: the workforce identity provider ID.\n2. Create the redirect URL. It is formatted as follows:\n\n https://auth.cloud.google/signin-callback/locations/global/workforcePools/\u003cvar translate=\"no\"\u003eWORKFORCE_POOL_ID\u003c/var\u003e/providers/\u003cvar translate=\"no\"\u003eWORKFORCE_PROVIDER_ID\u003c/var\u003e\n\n3. Configure your IdP with the redirect URL.\n\n In your IdP, enter the redirect URL. The field into which you enter the\n URL can vary. \n\n ### OIDC\n\n In your IdP, the field might be called `Redirect URL` or `Callback URL`.\n\n Your IdP sends the response and name token to this URL.\n\n ### SAML\n\n In your IdP, the field might be called `Single sign-on URL` or\n `SAML assertion consumer service (ACS) URL`.\n\n Your IdP posts the SAML assertion to this URL.\n\n If you want to enable IdP-initiated login with your SAML provider, enter the\n following URL in the `Default RelayState` setting, or its equivalent. The\n IdP redirects your user to this URL after your user successfully\n authenticates: \n\n https://console.cloud.google/\n\nInform your users how to sign in\n--------------------------------\n\nThis section describes the different ways your users can sign in to the\nconsole (federated).\n\n### Start the sign-in process using an SSO link\n\nTo start the sign-in process with your IdP, you can share a link with your users\nthat redirects them to your IdP without prompting them for the provider name.\nAfter users successfully login, they are automatically redirected to the\nconsole (federated).\n\nTo use this method, send the following login link to your users: \n\n https://auth.cloud.google/signin/locations/global/workforcePools/\u003cvar translate=\"no\"\u003eWORKFORCE_POOL_ID\u003c/var\u003e/providers/\u003cvar translate=\"no\"\u003eWORKFORCE_PROVIDER_ID\u003c/var\u003e?continueUrl=https://console.cloud.google/\n\n### Start the sign-in process using the console (federated)\n\nTo start the sign-in process at the console (federated), do the\nfollowing:\n\n1. Provide your users with your workforce identity pool provider name\n described earlier in this document.\n\n2. Provide your users with the following link to the\n console (federated):\n\n https://console.cloud.google/\n\nWhen your users first access the console (federated), they are prompted\nto enter the workforce identity pool provider name. They are then redirected to\nyour IdP to authenticate. After they authenticate, they are redirected back to\nthe console (federated).\n\n### Use SAML IdP-initiated sign-in\n\nThe SAML specification defines a flow called [IdP-initiated sign-in](https://auth0.com/docs/authenticate/protocols/saml/saml-sso-integrations/configure-idp-initiated-saml-sign-on-to-oidc-apps),\nin which users initiate the sign-in process at the IdP. If your IdP supports\nthis flow, you can share the details with your users.\n\nUse the console (federated) vs. the Google Cloud console\n--------------------------------------------------------\n\nThe [console (federated)](https://console.cloud.google/) provides limited\naccess to only those Google Cloud products that support\nWorkforce Identity Federation. Because of this, when using the\nconsole (federated), you see a limited number of Google Cloud\nproducts, and the product UIs themselves might have further limitations when\nviewed in the console (federated).\n\nTo learn more about products that support Workforce Identity Federation and\nrelated limitations, see [Identity federation: supported products and limitations](/iam/docs/federated-identity-supported-services).\n\nThe Google Cloud console, by comparison, can provide full access to all products and\nfeatures, depending on roles granted to users.\n\nWhat's next\n-----------\n\n- [Identity federation: supported products and limitations](/iam/docs/federated-identity-supported-services)"]]