Workforce Identity Federation

Related topics

• Cloud Identity is an alternative to Workforce Identity Federation From the official documentation: “To reduce complexity, we recommend using either Cloud Identity or Workforce Identity Federation.”
• Identity and Access Management works with Workforce Identity Federation From the official documentation: “Workforce Identity Federation lets you use an external identity provider (IdP) to authenticate and authorize a workforce—a group of *users*, such as employees, partners, and contractors—using IAM, so that the users can access Google Cloud services.”
• Identity-Aware Proxy works with Workforce Identity Federation From the official documentation: “Learn how to [configure IAP with Workforce Identity Federation](/iap/docs/use-workforce-identity-federation).”
• workforce identity pool is part of Workforce Identity Federation From the official documentation: “For Security Token Service API requests where the audience is a [Workforce Identity Federation](/iam/docs/federated-identity-supported-services) pool (which is an organization-level resource), you must configure egress rules.”
• Cloud SQL works with Workforce Identity Federation From the official documentation: “Workforce Identity Federation lets you use your existing identity provider (IdP), such as Microsoft Active Directory or Okta, to access Cloud SQL instances without requiring a Google Account.”
• IAM works with Workforce Identity Federation From the official documentation: “Workforce Identity Federation supports multiple protocols, doesn't install components in the cluster, and is integrated with IAM.”
• OS Login works with Workforce Identity Federation From the official documentation: “Connect to VMs that use OS Login with workforce identity federation using the Google Cloud console, the gcloud CLI, or other SSH clients.”
• Workforce Identity Federation depends on Cloud Logging From the official documentation: “However, Workforce Identity Federation detailed audit logging uses Cloud Logging.”
• Workforce Identity Federation is part of Identity and Access Management From the official documentation: “Workforce Identity Federation is an IAM feature that lets you authenticate to Google Cloud from any external IdP that supports OIDC or SAML 2.0.”
• Workforce Identity Federation depends on Identity and Access Management From the official documentation: “Workforce Identity Federation lets you use an external identity provider (IdP) to authenticate and authorize a workforce—a group of *users*, such as employees, partners, and contractors—using IAM, so that the users can access Google Cloud services.”
• workforce identity pool provider is part of Workforce Identity Federation From the official documentation: “To configure Workforce Identity Federation, you create 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).”
• Cloud Logging works with Workforce Identity Federation From the official documentation: “Errors at this stage are often visible in Cloud Logging for Workforce Identity Federation.”
• Google SecOps depends on Workforce Identity Federation From the official documentation: “Google SecOps requires using Workforce Identity Federation as the SSO broker for a varied set of use cases.”
• Google SecOps works with Workforce Identity Federation From the official documentation: “For customers who use Workforce Identity Federation, see [Map users in the Google SecOps platform using Identity Providers (IdPs)](/chronicle/docs/soar/admin-tasks/user-secops/map-users-in-the-secops-platform).”
• VPC Service Controls works with Workforce Identity Federation From the official documentation: “VPC Service Controls supports only specific <a href="/vpc-service-controls/docs/supported-identities">Workforce Identity Federation and Workload Identity Federation principal identifiers</a>.”
• Workforce Identity Federation depends on Access Context Manager From the official documentation: “Workforce Identity Federation uses Access Context Manager Google Cloud access bindings to configure extended session length:”
• Workforce Identity Federation is part of Apigee From the official documentation: “**Dashboard availability:** This dashboard is not available if your Apigee organization was provisioned with compliance-related Apigee features, such as [data residency](/apigee/docs/api-platform/get-started/drz-concepts)…”
• Workforce Identity Federation secures Apigee From the official documentation: “Workforce Identity Federation can be used across Google Cloud and provides a single point of control for managing access to Apigee.”
• Workforce Identity Federation is part of IAM From the official documentation: “Workforce Identity Federation is an IAM feature and only lets users access services that use IAM.”
• workforce identity pool depends on Workforce Identity Federation From the official documentation: “A workforce identity pool is a set of user identities that is managed by an external IdP and federated by using [Workforce Identity Federation](/iam/docs/workforce-identity-federation).”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
• Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• Cloud Run works with Secret Manager From the official documentation: “You can integrate Secret Manager with other Google Cloud products such as Cloud Run.”
• Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Identity-Aware Proxy secures Cloud Run From the official documentation: “There are two ways to enable Identity-Aware Proxy for your Cloud Run services.”
• workforce identity pool provider is part of workforce identity pool From the official documentation: “Use a single provider per pool to avoid subject collisions”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• IAM secures BigQuery From the official documentation: “BigQuery uses IAM to manage access to resources.”
• Identity and Access Management works with OS Login From the official documentation: “OS Login lets you to manage access to instances using IAM.”
• Cloud SQL works with Secret Manager From the official documentation: “Secret Manager attempts to update the credentials in your Cloud SQL instance.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
• Identity-Aware Proxy secures Compute Engine From the official documentation: “Securing Compute Engine apps Enable IAP for Compute Engine apps.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Run works with Identity-Aware Proxy From the official documentation: “On the Cloud Run security page, find the checkbox for Identity-Aware Proxy (IAP).”
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• Compute Engine works with Identity-Aware Proxy From the official documentation: “Set up a Compute Engine instance with IAP.”
• Identity and Access Management works with Identity-Aware Proxy From the official documentation: “The IAP API lets you to apply IAM permissions to individual resources in an IAP-secured project.”
• OS Login is part of Compute Engine From the official documentation: “Require OS Login on Compute Engine Instances”
• VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
• Apigee works with Compute Engine From the official documentation: “| [Compute Engine](https://console.cloud.google.com/apis/library/compute.googleapis.com) | `compute.googleapis.com` | Used for managing your Apigee runtime. |”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”