Auth0 and Dome
Your app signs users in, and Dome checks every call made for them. An agent sends the user's Auth0 access token with each call. Dome verifies it against your tenant, and rules decide on the user's email and the claims your Action adds. Audit records the agent and the user, every time.
Dome provides verified identityand access control with Auth0.
Verified on every call
Dome checks the token's signature against your tenant's keys, its issuer and its expiry. Tokens signed with HS256 are refused.
Rules read the user
The user's subject and email reach every rule. Claims your Action adds reach rules too.
Custom claims, by name
A namespaced string claim is readable by name. Map a namespaced list to roles or groups, and rules read it as a list.
Auth0in three steps.
Register your Auth0 tenant with Dome, add the claims rules need in an Action, and have the agent pass the token on. Dome needs no Auth0 credentials of its own.
Register your tenant as a verification provider
The issuer is your tenant domain with a trailing slash. Pin the audience to your API's identifier.
shelldome verification-providers create \ --name app-auth0 \ --method oidc \ --oidc-url https://<tenant>.auth0.com/ \ --oidc-expected-audience <api-identifier>Add claims in a post-login Action
Auth0 reserves groups and roles, so put roles in a namespaced claim and map it to roles in the verification provider. Call api.accessToken.setCustomClaim for email, and for a namespaced string such as https://example.com/team.
Read a namespaced claim in a rule
String claims arrive under principal.act_as.claims. Test that the claim is there before you compare it.
cedarprincipal has act_as &&principal.act_as has claims &&principal.act_as.claims has "https://example.com/team" &&principal.act_as.claims["https://example.com/team"] == "platform"
A ruleon the user's email.
Only users with an example.com address may have the agent open pull requests. Everyone else can still use it to read.
cedar
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "github" && resource.tool_name == "create_pull_request"}unless { principal has act_as && principal.act_as has email && principal.act_as.email like "*@example.com"};One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Acting for
agent dev-assistant · acting as a.okafor@example.com
github/create_pull_request(owner: "acme", repo: "web", head: "fix-login")
- CallerToken verified against app-auth0
- Emaila.okafor@example.com
- RulePull requests are open to example.com
DecisionAllowed
Bringing it alltogether.
Connecting Auth0 to registered agents, tools, and models in Dome completes a governed agent application.
Acting for
Auth0Identity
Agent
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
Models
Common questionsabout Auth0.
More of whatDome works with.
Model
Claude Fable
Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider
Anthropic
The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server
Atlassian
The Atlassian Rovo MCP server behind the Tool Gateway, with rules that decide each Jira and Confluence call on its tool and site.
Runtime
LangGraph
LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Client
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Agent service
TinyFish
TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.
Talk with ourFDE team.
Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.
Talk with our FDE team
Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.
Identity providers for AI agents: a verified person on every call
Your identity provider already knows your people. Dome verifies that identity on every agent call, so rules and audit name the person an agent acted for.