---
format: "aidr-story-markdown/v1"
id: "070a0f2f3b2e432220e86e03f647e267185bc0eea15eb7f172951a91ddb9dfd6"
canonical_url: "https://aidr.today/070a0f2f?lang=en"
title: "How to handle user, connector, and agent auth in Gemini Enterprise with a custom UI"
lang: "en"
requested_lang: "en"
available_langs: ["en","vi"]
translation_fallback: null
fallback_fields: []
published_at: "2026-11-20T20:29:14.000Z"
category: "Tools"
topics: ["google","agent","devtools"]
source_urls: []
summary: "Developers building a custom enterprise UI on top of Gemini Enterprise's :streamAssist API must manually implement three authentication layers. These include authenticating users or workloads via Google Identity or Workforce/Workload Identity Federation, managing third-party 3-legged OAuth for Federated Connectors through the Keystore, and configuring on-demand per-tool OAuth for custom ADK agents."
---

# How to handle user, connector, and agent auth in Gemini Enterprise with a custom UI

> [Open the canonical story](<https://aidr.today/070a0f2f?lang=en>)

**Published:** 2026-11-20T20:29:14.000Z
**Category:** Tools
**Topics:** google, agent, devtools

## Summary

Developers building a custom enterprise UI on top of Gemini Enterprise's :streamAssist API must manually implement three authentication layers\. These include authenticating users or workloads via Google Identity or Workforce/Workload Identity Federation, managing third\-party 3\-legged OAuth for Federated Connectors through the Keystore, and configuring on\-demand per\-tool OAuth for custom ADK agents\.

## Sources

_No safe source URL was recorded._

