Watch the 60-second introduction video (MP4)
Agent Auth is a standards-oriented authorization server built for software that acts on behalf of people or other workloads. It gives agents an explicit, auditable way to obtain resource-bound access tokens instead of sharing user credentials or relying on opaque, application-specific authorization.
The project combines a Rust protocol core, an AWS serverless deployment, resource-server SDKs, and a React administration UI. It supports conventional OAuth and OIDC clients while adding first-class authorization boundaries for agents, machine identities, delegation chains, and MCP resources.
[!IMPORTANT] Agent Auth
v1.1.0is the current stable source release. Semantic Versioning covers the HTTP API described byopenapi/openapi.jsonand the TypeScript and Python resource-server SDK APIs; deployment configuration and persisted data formats are outside that guarantee. Review the conformance matrix, deployment design, and security assumptions before using it in a production environment. Project tests are not a certification by the OpenID Foundation or another standards body.
Current Status
- Release —
v1.1.0is the current stable source release. See the release notes for its changes. Release assets are source archives; Rust crates remain unpublished. The resource-server SDKs are published separately asagent_auth_rs1.0.2 on npm and PyPI. SDK distribution and release qualification records verified public artifact digests, source/tag identity and independent installation checks for the npm tarball and Python wheel/sdist. - Repository evidence — every completed row in the conformance matrix must map to exact automated selectors that CI actually runs. Broad suites, comments, and historical results do not count as exact evidence.
- External release gate — the
external conformance contract runs the fixed
OIDF Basic OP code-flow plan plus project-owned selected RFC 9700
regressions. Non-
PASSEDofficial outcomes require explicit, repository-bound, time-limited exceptions; a green gate is not standards-body certification. - Third-party interoperability — sanitized live evidence from a real Okta SCIM directory job and a real Okta Cross App Access ID-JAG exchange is recorded in the conformance matrix (C12.2 and C13.8). These are recorded runs, not part of the daily external release gate.
Why Agent Auth?
Traditional identity systems generally assume a human user and a pre-registered web application. Agent systems introduce a different set of questions:
- Which agent or workload is requesting access?
- Is it acting for itself, for a user, or through a delegation chain?
- Which resource server may receive the token?
- What scopes and structured authorization constraints apply?
- How can a resource server validate the token without sharing secrets?
- How are tenant, issuer, key, and audit boundaries preserved?
Agent Auth makes these decisions part of the authorization-server contract. Tokens are bound to an explicit resource and audience, subject and actor types are represented directly, and security-sensitive behavior is backed by executable conformance requirements.
Highlights
- OAuth 2.1 and OIDC foundations — authorization code with PKCE, refresh token rotation, discovery, authorization-server metadata, UserInfo, client credentials, device authorization, CIBA, and token exchange.
- Agent and workload identity — authenticate workloads with AWS SigV4, OIDC assertions, SPIFFE JWT-SVIDs, or X.509-SVID mTLS profiles.
- MCP-aware authorization — issue single-audience, resource-bound access tokens and publish protected-resource metadata for MCP resource servers.
- Explicit delegation — represent user, agent, service, grant, actor-chain, scope, and rich-authorization constraints without hiding them in application-specific session state.
- Modern client security — Dynamic Client Registration, RFC 7592 client management, PAR, DPoP, exact redirect validation, and downgrade controls.
- Enterprise integration — upstream OIDC and SAML federation, passkeys, SCIM provisioning, security-event delivery, and administrative workflows.
- AWS-native deployment — Rust on Lambda behind API Gateway and CloudFront, with DynamoDB authority stores, KMS-backed signing, and AWS CDK infrastructure.
- Resource-server SDKs — TypeScript and Python packages for JWT, audience, issuer, scope, DPoP, and discovery validation.
- Executable specification — normative requirements are linked to exact automated test selectors and CI jobs.
For the precise status and evidence for each capability, use
docs/CONFORMANCE.md rather than this summary.
Architecture
The protocol and policy logic is separated from AWS adapters. The same core can run locally with in-memory stores, as a self-hosted single-tenant deployment, or with tenant-aware issuer, storage, policy, quota, and key boundaries.
Read docs/DESIGN.md for the protocol model and
docs/DEPLOYMENT.md for trust boundaries and deployment
topology.
Quick Start
Prerequisites
- Rust 1.85 or newer
curljq
Run the local development server
git clone https://github.com/amliuyong/a-auth.git
cd a-auth
cargo run -p agent-auth-http --bin agent-auth-server
The development server listens on 127.0.0.1:8080 and uses in-memory stores;
it does not require an AWS account.
In another terminal:
curl --silent http://localhost:8080/.well-known/openid-configuration | jq
Use localhost, not 127.0.0.1, in protocol requests because the local issuer
is derived from the validated request host.
The complete local Authorization Code + PKCE walkthrough is in
docs/GETTING_STARTED.md.
Deployment
The included AWS CDK application supports a self-hosted deployment and the tenant-aware topology described in the deployment documentation.
Start with a synthesis, which does not deploy resources:
cd infra
npm ci
npm run build
npx cdk synth
Before deploying, read docs/INSTALL_DEPLOY.md. It
covers prerequisites, configuration, domains, keys, migration steps, validation,
and teardown. AWS deployments can create billable resources.
Repository Layout
Development
Enable the repository hook after cloning:
git config core.hooksPath .githooks
Common checks:
cargo fmt --all -- --check
cargo test --workspace --lib --locked
npm ci
npm run lint:markdown
cd infra
npm ci
npm test
The CI workflow also checks Clippy, AWS adapters, exact conformance selectors, the web application, infrastructure, OpenAPI drift, and both resource-server SDKs.
When changing protocol behavior, update the relevant implementation, tests,
OpenAPI surface, specification, and conformance evidence together. See
CONTRIBUTING.md for the contribution workflow.
Documentation
Security
Security vulnerabilities must not be reported in a public issue. Use GitHub
private vulnerability reporting as described in SECURITY.md.
Never commit real credentials, tokens, personal data, AWS account identifiers, production domains, or deployment evidence. Examples and tests must use synthetic values.
Contributing
Issues and pull requests are welcome. Please read
CONTRIBUTING.md before submitting a change. Contributions
that affect wire behavior should include focused tests and corresponding
documentation or conformance updates.
简体中文简介
Agent Auth 是一个面向 AI agent、workload 和 MCP Resource Server 的 OAuth 2.1 / OpenID Connect 授权服务器。它重点解决“谁在代表谁、可以访问哪个资源、 经过了怎样的委托链、资源服务器如何独立验证权限”等 agent 授权问题,同时兼容 传统 OAuth/OIDC 客户端。
当前稳定源码版本为
v1.1.0。
项目采用 Rust 实现协议与策略核心,提供 AWS CDK 部署、React 管理界面以及
TypeScript/Python Resource Server SDK。1.0 起按语义化版本对 HTTP API
(openapi/openapi.json)与 TypeScript/Python Resource Server SDK 做兼容承诺,
部署配置与持久化数据格式不在承诺范围内;
生产使用前请审阅 docs/CONFORMANCE.md、
docs/DESIGN.md 和
docs/INSTALL_DEPLOY.md。
60 秒介绍视频见 docs/assets/agent-auth-intro.mp4。
中文读者建议从 docs/GETTING_STARTED.md 开始,
再按角色阅读 docs/USER_GUIDE.md 或部署文档。
License
Licensed under the Apache License 2.0.