How to handle user, connector, and agent auth in Gemini Enterprise with a custom UI
Blog post from Google Cloud
Custom Gemini Enterprise interfaces that call the StreamAssist API must manage authentication flows handled automatically by the standard web application. Human-facing applications can authenticate users directly with Google Identity or use Workforce Identity Federation through Google STS, preserving individual permissions, document access controls, and user-specific features; shared, non-personalized services can use Workload Identity Federation, which represents a machine rather than an individual. Callers also need the Discovery Engine User role, and human users require an active Gemini Enterprise license. For Federated Connectors such as Drive, SharePoint, Jira, and ServiceNow, the custom interface must support per-user three-legged OAuth consent, while Gemini Enterprise’s Keystore securely manages refresh tokens and enables live searches using authorized access. Custom ADK agents that call protected tools can instead use on-demand, tool-specific OAuth through GCP Auth Manager’s Token Vault and Agent Identity, avoiding upfront authorization for every tool; after consent, the query is retried with the saved credentials. The accompanying code repository provides examples and test utilities for all three authentication layers.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| AI Agents | 10 | 6,233 | 1,230 | 245 | -11% |
| Secrets Management | 10 | 2,876 | 539 | 148 | -7% |
| Platform Engineering | 4 | 1,295 | 290 | 84 | -36% |
| Real-time | 2 | 3,194 | 698 | 199 | -24% |
| Multi-agent systems | 1 | 173 | 95 | 52 | -47% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.