OAuth 2.0

Related topics

• Apigee works with OAuth 2.0 From the official documentation: “Learn about the main advantages of using OAuth 2.0 with Apigee, including speed, scale, visibility, and so on.”
• 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.”
• JSON Web Token is an alternative to OAuth 2.0 From the official documentation: “- For workload authentication, use OAuth 2.0 or signed JSON Web Tokens (JWTs).”
• OAuth 2.0 depends on scopes From the official documentation: “OAuth 2.0 uses *scopes* to determine if an authenticated identity is authorized.”
• OAuth 2.0 is an alternative to service account From the official documentation: “If you are using the service account authentication instead of OAuth 2.0 authentication, ensure that appropriate permissions are given to the service account.”
• 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.”
• scopes is part of OAuth 2.0 From the official documentation: “Through the mechanism of scopes, OAuth 2.0 can grant an app limited access to protected resources.”
• Compute Engine works with service account From the official documentation: “A common method is to attach a service account to a resource like a Compute Engine instance.”
• 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.”
• Identity-Aware Proxy secures Cloud Run From the official documentation: “IAP provides a central authorization layer for HTTPS applications deployed to Cloud Run.”
• 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.”
• 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 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:”
• Cloud Run works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• 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.”
• 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 Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Compute Engine works with Identity-Aware Proxy From the official documentation: “Set up a Compute Engine instance with IAP.”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
• Identity-Aware Proxy works with service account From the official documentation: “Authenticate a service account to access resources secured by IAP.”
• Secret Manager works with service account From the official documentation: “The service account can access the secret data.”
• service account depends on Secret Manager From the official documentation: “Make sure that the service account that AlloyDB Omni uses has the `secretmanager.secretAccessor` permission to read the secret from Secret Manager.”
• Apigee works with BigQuery From the official documentation: “You can use the Apigee API to export all analytics data for an entire day from Apigee to your own data repository, such as Google Cloud Storage or BigQuery.”
• Apigee works with Cloud Run From the official documentation: “Apigee supports using [Google OAuth tokens](https://developers.google.com/identity/protocols/oauth2) or [OpenID Connect tokens](https://developers.google.com/identity/protocols/oauth2/openid-connect) to authenticate with Google services such as [Cloud…”
• Apigee is an alternative to Cloud Run From the official documentation: “You can also publish your own remote MCP servers using [Apigee](/apigee/docs/api-platform/get-started/what-apigee) or [Cloud Run](/run/docs/host-mcp-servers).”
• Apigee works with Secret Manager From the official documentation: “Apigee supports using [Google OAuth tokens](https://developers.google.com/identity/protocols/oauth2) or [OpenID Connect tokens](https://developers.google.com/identity/protocols/oauth2/openid-connect) to authenticate with Google services such as [Cloud…”
• 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.”
• BigQuery works with Compute Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• BigQuery works with service account From the official documentation: “The service account can be used by services, such as Cloud Run, to read and modify data in the BigQuery dataset.”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run works with Identity-Aware Proxy From the official documentation: “Enable IAP on the Cloud Run service.”
• 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.”
• 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.”
• Compute Engine depends on service account From the official documentation: “The Service Account is used by Compute Engine to access other Google APIs.”
• Identity and Access Management secures BigQuery From the official documentation: “Security in BigQuery is intrinsically linked to [Identity and Access Management (IAM)](/iam/docs/overview) in Google Cloud.”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
• 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).”
• Identity-Aware Proxy secures Compute Engine From the official documentation: “Securing Compute Engine apps Enable IAP for Compute Engine apps.”
• Identity-Aware Proxy depends on JSON Web Token From the official documentation: “When configured, Identity-Aware Proxy (IAP) uses JSON Web Tokens (JWT) to make sure that a request to your app is authorized.”
• Identity-Aware Proxy works with OpenID Connect From the official documentation: “When making requests to an endpoint, use OIDC to authenticate through IAP.”
• JSON Web Token works with service account From the official documentation: “The calling service uses the service account's private key to sign a secure [JSON Web Token (JWT)](https://jwt.io/) and sends the signed JWT in the request to your API.”
• Secret Manager secures Cloud Run From the official documentation: “Store sensitive credentials in Secret Manager for secure access by the Cloud Run function.”
• service account depends on BigQuery From the official documentation: “Each feature view uses a service account to access the source data in BigQuery during sync.”
• Workload Identity Federation is part of Identity and Access Management From the official documentation: “[Identity and Access Management (IAM)](/iam/docs/overview) lets you manage fine-grained access to services and resources in Google Cloud. IAM includes features such as the following: - [Privileged Access Manager](/iam/docs/pam-overview), which manages on-demand, temporary…”
• 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.”