---
title: "Authorization"
description: "4 posts about Authorization, summarised, each linking to the original."
---

# Authorization
> 4 posts about Authorization, summarised, each linking to the original.

## Articles

### [Now GA: Building permission-aware Databricks Apps with on-behalf-of-user authorization](https://yomu.fyi/post/now-ga-building-permission-aware-databricks-apps-with-on-behalf-of-use.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Aakrati Talati, Cynthya Peranandam, Tushar Madan, Evan Pandya, Theo Fernandez
- Published: Oct 7, 2026
- Type: Announcement

Databricks Apps now generally supports on-behalf-of-user (OBO) authorization, enabling apps to act using the signed-in user’s identity so Unity Catalog enforces existing data permissions including row filters and column masks. Developers choose between app authorization for app-owned operations and user authorization for user-specific data access, with API scopes such as sql:restricted-query limiting what the app can do on the user’s behalf. The forwarded user access token is short-lived and per-request, passed via the x-forwarded-access-token HTTP header to the SQL connector, and the app must never store it. Workspace administrators can set an allowlist of API scopes, providing two levels of control: the app declares minimum scopes and the workspace defines the maximum, with account administrators able to add scopes outside the allowlist. The post recommends keeping app-owned and user-authorized clients separate in code and failing closed when a user token is missing to avoid returning results with incorrect permissions.


### [Confused Deputy: The Old Bug That AI Agents Keep Reintroducing](https://yomu.fyi/post/confused-deputy-the-old-bug-that-ai-agents-keep-reintroducing.md)
- Company: [Auth0](https://yomu.fyi/company/auth0.md)
- Author: Andrea Chiarelli
- Published: Sep 22, 2026
- Type: Explainer

The Confused Deputy problem, first documented in 1988, describes a program with legitimate authority being tricked into misusing that authority on behalf of a less-privileged actor. AI agents are particularly vulnerable because they process instructions and untrusted content through the same natural-language channel, making prompt injection straightforward. The post traces this pattern through CSRF, SSRF, and recent attacks like Clinejection, where an issue-triage bot executed an attacker-supplied command from a crafted issue title. That attack led to a poisoned GitHub Actions cache and a compromised npm package downloaded 4,000 times. The fix involves task-scoped short-lived credentials, capability-scoped permissions, credential isolation from the model, and human-in-the-loop approval for high-risk actions.


### [Auth0 Agent Gateway: The Identity Control Plane for Customer-Facing AI](https://yomu.fyi/post/auth0-agent-gateway-the-identity-control-plane-for-customer-facing-ai.md)
- Company: [Auth0](https://yomu.fyi/company/auth0.md)
- Author: Andrés Aguiar
- Published: Sep 18, 2026
- Type: Announcement

Auth0 Agent Gateway is announced in beta as a Customer Identity and Access Management (CIAM) control plane for governing product-native, customer-facing AI agents in multi-tenant SaaS applications. It addresses a trust model involving organizations, delegated user access, customer consent, independently owned connected accounts, and cross-tenant data boundaries, rather than workforce-only identity. Positioned between an agent and its tools, the gateway evaluates each call using agent, user, and organization context; it uses Organizations, Agents as Principals, Token Vault, token exchange, tenant logs, and administrative controls. The described capabilities include short-lived agent-only tokens, user-scoped credentials, runtime tool authorization, audit logging with optional SIEM streaming, and an agent kill switch. Auth0 is seeking product and engineering teams to join the beta.


### [Role-Based Access Control for humans and agents](https://yomu.fyi/post/role-based-access-control-for-humans-and-agents.md)
- Company: [Modal](https://yomu.fyi/company/modal.md)
- Published: May 27, 2026
- Type: Announcement

Modal announced Role-Based Access Control for Team and Enterprise users, enabling teams to grant agents and humans precise workspace access within Environments. Environments are workspace subdivisions with dedicated storage, apps, and limits, commonly set as dev-staging-production or per-developer. These now act as enforceable security boundaries through Restricted Environments, where workspace members are read-only by default and only explicitly assigned users or service users can deploy or manage resources. The RBAC system distinguishes human developers, AI agents, CI deployers, and external callers with recommended identities and environment access patterns, such as service users for agents and proxy auth tokens for external callers. Built on a new permissions architecture running for months, RBAC ties into Audit Logs and is the first of planned tools; future additions include spending limits and programmatic permissions.