Keycloak-compatible Identity & Access Management in Rust with DPoP and CIBA out of the box — OpenID Certified OIDC/OAuth2, shipped as a single binary, horizontally scalable
issuerd is an identity control plane for the agentic era: it governs human and
non-human identities alike — users, services, workloads and AI agents — with
least-privilege, short-lived, sender-constrained tokens and phishing-resistant
authentication by default.
OpenID Certified OIDC/OAuth2
The official OpenID Foundation registries list 10 OP profiles on v0.1.17
plus RP-Initiated Logout OP on v0.1.19 (OIDC,
logout).
The accepted submissions used the hosted conformance suite (release v5.3.3).
Separately, the latest self-hosted release v5.3.3 engineering matrix covers
43 plan invocations and 612 modules with 0 unexpected failures and 0
unexpected warnings. Read the conformance and certification guide.
Every release ships an attested
conformance report bundle. Advanced OAuth 2.1 capabilities included:
PAR, JAR/JARM, RAR, DPoP, CIBA, token exchange, dynamic client registration.
Keycloak-compatible
The realm model, role claims (realm_access / resource_access), the Admin
REST API shape, adapter-config downloads, and kc_idp_hint behave the way your
existing Keycloak integrations expect. Every deliberate difference is
documented in tests/KEYCLOAK_DIFFS.md.
Fast and small
Faster than Keycloak 26.7 in every measured k6 scenario — up to 7.8× the
throughput, ~6× less memory, and an 8.7× smaller image. One self-contained
Rust binary; #! [forbid(unsafe_code)] across the whole workspace.
Scales horizontally
Shared state lives in PostgreSQL + Redis, and storage-backed signing keys are
shared by every node. Run a single binary or a multi-node cluster behind a
load balancer — a two-node demo stack ships in the repo.
Built for AI agents
DPoP sender-constrained tokens, RFC 8693 per-call attenuation, and CIBA
step-up approval. The built-in realm-scoped MCP server adds 67 curated tools
and three redacted resources: ordinary actions stay within roles and scopes,
while strict operations require one fresh human approval for one exact
operation. Any LLM can participate through a compatible MCP client.
MCP guide · exact-operation security article.
Federation & MFA included
LDAP, Active Directory, and Kerberos/SPNEGO user federation; identity brokering
with Google, GitHub, and Microsoft; TOTP, WebAuthn/passkeys for
phishing-resistant MFA, and email-code
login. No enterprise edition — everything is in the open repository.
Get startedDocker demo stack or build from source — first realm and first token in minutes.
One approval, one exact operationHow the built-in MCP server keeps any model inside server-enforced policy and binds dangerous actions to exact human approval.
OIDC conformance & certificationThe 11-profile version matrix, hermetic test environment, hosted evidence, and lessons from the v0.1.19 resubmission.
Documentation overviewDeployment, administration, agentic IAM, federation, and operations guides.