---
title: "OAuth"
description: "3 posts about OAuth, summarised, each linking to the original."
---

# OAuth
> 3 posts about OAuth, summarised, each linking to the original.

## Articles

### [How to handle user, connector, and agent auth in Gemini Enterprise with a custom UI](https://yomu.fyi/post/how-to-handle-user-connector-and-agent-auth-in-gemini-enterprise-with.md)
- Company: [Google](https://yomu.fyi/company/google.md)
- Author: Neeraj Agrawal
- Published: Nov 20, 2026
- Type: Tutorial

Enterprises building a custom UI to embed Gemini Enterprise must handle three authentication flows that the built-in web app automates. For StreamAssist authentication, three patterns are available: Google Identity for Google Workspace users, Workforce Identity Federation for external IdP users, and Workload Identity Federation for backend bots. Federated Connectors require a two-phase 3LO flow where Customer BE checks the Keystore for tokens and triggers a consent popup when needed. Custom ADK agents use on-demand 3LO by wrapping protected sub-agent tools with GcpAuthProvider and deploying with Agent Identity. The guide provides runnable code for all three layers in a GitHub repository.


### [Securing Your Newest Customer Channel with Auth for Personal Agents](https://yomu.fyi/post/securing-your-newest-customer-channel-with-auth-for-personal-agents.md)
- Company: [Auth0](https://yomu.fyi/company/auth0.md)
- Published: Nov 18, 2026
- Type: Announcement

Personal agents like Meta’s Muse and xAI’s Grok Bot have rapidly gained adoption, with over 10 million Muse users in the US and Canada within six weeks. These agents typically collect and replay user credentials, which is insecure, breaks with passkeys or MFA, and grants full account access. Auth0 is introducing Auth for Personal Agents, an identity solution that supports the Personal Agent Protocol (Poppy). Poppy is an open protocol built on OAuth and JWTs that lets agents identify themselves via a Client ID Metadata Document (CIMD) and receive scoped, revocable, DPoP-bound tokens. Brands can verify the agent, delegate customer sign-in through their own login, and enforce granular permissions, enabling secure agent-driven interactions without blocking the channel.


### [Slack Bots on Sprites: OAuth is Easy Now](https://yomu.fyi/post/slack-bots-on-sprites-oauth-is-easy-now.md)
- Company: [Fly.io](https://yomu.fyi/company/fly-io.md)
- Published: Nov 6, 2026
- Type: Tutorial

Building a Slack bot with OAuth usually requires setting up a server with a public URL, handling callbacks, storing tokens, and maintaining them across restarts. Sprites simplifies this by providing an internet-accessible environment with a persistent filesystem, eliminating the need for Ngrok or separate hosting. To create the bot, users initialize npm, install @slack/bolt and express, and build an OAuth handler for Slack’s callback that stores tokens to the filesystem. The bot is registered as a Sprite service with sprite-env services create , which enables auto-start on HTTP requests, automatic request routing to port 8080, and persistent registration across hibernations. When idle, the Sprite hibernates to save costs and wakes in under a second, and users can create a checkpoint snapshot for easy restoration.
