In the news
How to handle user, connector, and agent auth in Gemini Enterprise with a custom UI- Google Developers Blog
Google Developers · Published · 3 min read
In 30 seconds
- What happened
- Google published guidance on handling three authentication layers when building custom UIs for Gemini Enterprise: user identity to StreamAssist, federated connector OAuth, and per-tool OAuth for custom agents.
- Why it matters
- Enterprise engineers building custom interfaces that embed Gemini Enterprise into internal portals or line-of-business applications need this to properly manage identity and access control.
- Watch out
- Custom UIs must manually implement authentication flows that the built-in web app handles automatically. Workload Identity patterns lose per-user document ACLs and connector permissions, suitable only for non-personalized bots.
- agent
- gemini
The patterns behind this
- MCP Gateway (Tool Federation & Governance)
- Web Bot Auth (Signed Agents)
- Authenticated Delegation & Agent Identity
Each one covers how the technique works, when it earns its cost, and where it breaks.
The Agent Architect
One pattern, one tradeoff, one production failure story. A short weekly briefing for people building agentic systems.
Weekly email, one-click unsubscribe. We only use your address to send the briefing.