OpenID Connect

Related topics

• Cloud Build works with OpenID Connect From the official documentation: “Cloud Build provides built-in support for the [OpenID Connect (OIDC)](https://openid.net/connect/) standard for secure authentication and authorization between services.”
• Cloud Run works with OpenID Connect From the official documentation: “Makes an authenticated request within a workflow, using OpenID Connect (OIDC) to connect with Cloud Run.”
• Identity-Aware Proxy works with OpenID Connect From the official documentation: “When making requests to an endpoint, use OIDC to authenticate through IAP.”
• Identity Platform works with OpenID Connect From the official documentation: “You can import users to all of the providers Identity Platform supports, including OAuth, SAML, and OIDC.”
• OpenID Connect depends on OAuth 2.0 From the official documentation: “OpenID Connect is an identity layer on top of the OAuth 2.0 protocol.”
• Workload Identity Federation depends on OpenID Connect From the official documentation: “To let your customers use Workload Identity Federation, your product or service must implement a subset of OpenID Connect.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
• App Engine is an alternative to Cloud Run From the official documentation: “App Engine and Cloud Run are Google Cloud platforms for hosting apps and services.”
• Cloud Run depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Identity-Aware Proxy secures App Engine From the official documentation: “Securing App Engine apps Enable IAP for App Engine apps.”
• Identity-Aware Proxy secures Cloud Run From the official documentation: “IAP provides a central authorization layer for HTTPS applications deployed to Cloud Run.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• GKE works with Identity-Aware Proxy From the official documentation: “If you are running GKE version 1.24 or later, you can configure IAP and GKE by using the Kubernetes Gateway API.”
• Identity-Aware Proxy works with Identity Platform From the official documentation: “IAP uses Identity Platform to authenticate external identities.”
• service account works with Workload Identity Federation From the official documentation: “When an application uses Workload Identity Federation, it impersonates a service account.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• GKE works with Workload Identity Federation From the official documentation: “To allow GitHub Actions authenticate Google Cloud and deploy to GKE, use [workload identity federation](/iam/docs/workload-identity-federation).”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management works with Identity-Aware Proxy From the official documentation: “IAP re-checks Identity and Access Management (IAM) authorization for all requests during valid sessions.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• App Engine works with Cloud Build From the official documentation: “Cloud Build builds your app and deploys it to App Engine.”
• App Engine works with Cloud Storage From the official documentation: “To use a Cloud Storage bucket from an App Engine app:”
• App Engine works with Identity-Aware Proxy From the official documentation: “Validate a JWT passed to your App Engine app by Identity-Aware Proxy.”
• App Engine works with Identity Platform From the official documentation: “You have successfully integrated Identity Platform with your App Engine application.”
• App Engine works with Pub/Sub From the official documentation: “Pub/Sub is now the preferred way of performing pull queue work in App Engine.”
• Cloud Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• GKE works with Pub/Sub From the official documentation: “GKE publishes upgrade notifications to [Pub/Sub](/pubsub/docs/overview), providing you with a channel to receive information from GKE about your clusters.”
• Identity-Aware Proxy works with service account From the official documentation: “Authenticate a service account to access resources secured by IAP.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• App Engine depends on Cloud Build From the official documentation: “In addition, all App Engine runtimes now use Cloud Build to build apps into a container during the deployment process.”
• App Engine depends on Cloud Storage From the official documentation: “App Engine creates a [default Cloud Storage multi-regional bucket](/appengine/docs/flexible/locations#cloud-storage-location) on your behalf on the same region where it creates your application. It requires this bucket to store the contents of your application.”
• App Engine is an alternative to Cloud Storage From the official documentation: “You can use durable storage like Cloud Storage or an in-memory cache like App Engine to share data between pipeline instances.”
• App Engine depends on service account From the official documentation: “App Engine applications require a [service account](/iam/docs/service-accounts) to access other Google Cloud services and execute tasks.”
• Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
• Cloud Build depends on GKE From the official documentation: “To deploy the application in your Kubernetes cluster, Cloud Build needs the Kubernetes Engine Developer [Identity and Access Management Role](/iam/docs/understanding-roles).”
• Cloud Build works with Pub/Sub From the official documentation: “Cloud Build sends all build event updates, along with build metadata, [to Pub/Sub](/build/docs/subscribe-build-notifications) on either the `cloud-builds` topic or a user-defined topic.”
• Cloud Build depends on service account From the official documentation: “Cloud Build uses a service account to execute builds on your behalf.”
• Cloud Run works with Identity-Aware Proxy From the official documentation: “Enable IAP on the Cloud Run service.”
• Cloud Run works with Identity Platform From the official documentation: “Use Identity Platform to authenticate an end user to the Cloud Run service backend.”
• Cloud Run works with service account From the official documentation: “Map a custom Service Account to a Cloud Run service”
• Cloud Run works with Workload Identity Federation From the official documentation: “This tutorial describes how to use Workload Identity Federation to authenticate workloads that run outside of Google Cloud so that they can access microservices hosted by Cloud Run.”
• Cloud Storage works with GKE From the official documentation: “This example configures GKE to store Pod snapshots in the `FOLDER_PATH/` path inside the Cloud Storage bucket `BUCKET_NAME`:”
• 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).”
• Cloud Storage works with Identity Platform From the official documentation: “This identity will then be used when accessing other Identity Platform services, such as Cloud Storage.”
• GKE depends on Identity and Access Management From the official documentation: “GKE relies on and can be used with many other Google Cloud services, from IAM for access control to Cloud Billing for managing your costs.”
• Identity and Access Management secures Cloud Build From the official documentation: “To grant other users access, you can grant Identity and Access Management (IAM) roles on the project, or on a specific Cloud Build resource.”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
• Identity and Access Management configures GKE From the official documentation: “First, as you would with most services on Google Cloud, you need to configure [IAM](/iam) roles in order to set up authorization on GKE.”
• Identity and Access Management secures Identity Platform From the official documentation: “Access control with IAM Identity and Access Management permissions and roles for Identity Platform.”
• Identity and Access Management works with OAuth 2.0 From the official documentation: “The Google Cloud CLI remote MCP server uses the [OAuth 2.0](https://developers.google.com/identity/protocols/oauth2) protocol with [Identity and Access Management (IAM)](https://docs.cloud.google.com/iam/docs/overview) for authentication and authorization.”
• Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management configures service account From the official documentation: “Learn more about using Identity and Access Management to [create a service account](/iam/docs/creating-managing-service-accounts) and [manage the access granted to a service account](/iam/docs/granting-changing-revoking-access).”