GCP Application Integration Updates Authorization for Integration Runs
GCP Application Integration is updating how identities are handled for integration runs, requiring explicit permissions. Each integration run will now act either as the triggering user or a specified run-as service account. Integrations not triggered by a person will require a configured service account. Users may need to take action to update affected integrations before the changes are enforced.
Notes (1) ›
- Application Integration Upcoming authorization changes for integration runs
Upcoming authorization changes for integration runs Application Integration is updating how identities are handled for integration runs. Every run will act as either the person who triggered it or a run-as service account that you configure, and running an integration will require permission to act as that service account. Integrations that run without a person, such as those started by a schedule or an event, will need an explicitly configured run-as service account. Action might be required before the change takes effect. For guidance on identifying affected integrations and updating them, s
https://docs.cloud.google.com/release-notes#August_28_2026
Related releases
- Google Cloud Developer Connect Insights & VPC SC Support Now GA Google Cloud release notes ·
- Compute Engine now offers LVM and EUS images for Red Hat Enterprise Linux Google Cloud release notes ·
- Managed Service for Apache Airflow Feature Orchestration Pipelines now GA Google Cloud release notes ·
- Google Cloud CCaaS 6.7 Delivers Email API for Bulk Updates and Bug Fixes Google Cloud release notes ·
- Apigee X Update 1-18-0-apigee-4 Improves Security and API Handling Google Cloud release notes ·
- BigQuery Enhances Compliance, Graph Processing, and XGBoost ML Capabilities Google Cloud release notes ·