Security

Reach services as the user

On-behalf-of (OBO) access exchanges the signed-in user's identity for a downstream token, so tools see the same permissions as that user. Use it for Microsoft Graph or an HTTP MCP server protected by Entra OBO or RFC 8693 token exchange.

For an MCP server:

[servers.internal]
transport = "http"
url = "https://internal.example.com/mcp"
obo = { scope = "internal-api", description = "Use the internal API as the signed-in user" }

Do not combine obo with shared auth. Configure the OBO vault key and identity provider at the platform level, and request only the downstream scope the tool needs.

See .

Next

Authenticate callers

JWTs, federated identity, and API keys - picking the flow that matches each client.

Verify configuration content

Prove that deployed agents, skills, and documents are the ones you approved.

On this page

Next