How to handle user, connector, and agent auth in Gemini Enterprise with a custom UI
How to handle user, connector, and agent auth in Gemini Enterprise with a custom UI
This guide explains how enterprises building a custom UI that calls the Gemini Enterprise StreamAssist API must handle three authentication layers themselves: user or workload identity to StreamAssist (Google Identity, Workforce Identity Federation, or Workload Identity Federation), Federated Connector 3-legged OAuth via the managed Keystore, and on-demand per-tool OAuth for custom ADK agents on Vertex AI Agent Engine using GcpAuthProvider and the GCP Auth Manager Token Vault. It details the component flows, IAM roles and licensing requirements, and a runnable code blueprint in the gemini-enterprise-custom-ui-auth GitHub repository.
Source: Google Developers Blog · developers.googleblog.com