Roadmap
What the current release includes, what the project is working on, and the specifications it is evaluating. There are no dates: an item moves from Next to Available when it ships, and the changelog records it.
-
[01] Available · shipped
Available
Shipped in the current release and documented.
- OpenID Connect and OAuth 2.0 Authorization code flow with PKCE, grants for services and devices, discovery, logout in three forms, dynamic client registration.
- FAPI 2.0 and CIBA Requests pushed and signed, tokens bound to a key or a certificate, approval on another device.
- SAML 2.0 identity provider and service provider Identity provider for your applications, service provider for an organisation.
- Passkeys, one-time codes and passwords Several credentials per user, and a minimum authentication level per tenant.
- Key management and encryption at rest Keys sealed by your key management service, or by a sodium key file, and rotated with no downtime.
- Docker image and compose file The application as it ships, tested by the conformance suite every week.
-
[02] Next · under development
Next
Under development, in no fixed order and with no date.
- SCIM provisioning Receiving the users and groups a directory pushes, first.
- Upstream OpenID Connect providers Google Workspace and Microsoft Entra ID, discovered from the email domain, as SAML is today.
- Keycloak import With the subject identifiers your clients already know.
- ProConnect The federation of the French public sector, and account linking.
- Administration console Clients, keys, users, sessions: what the console commands do today, as pages.
- Tenant audit view The audit log read across users, and the sessions of a user, revocable.
- Self-service sign-up and account recovery A user who enrols alone, and one who lost a credential.
- Hosted version Beffroi run for you, with a control plane. An instance you host can be operated from it too: the instance calls out, nothing calls in.
- Helm chart For Kubernetes, next to the compose file.
- OpenID Certification The filing with the foundation, for the plans that already run.
-
[03] Exploring · under evaluation
Exploring
Specifications the project follows, with no implementation planned until a deployment needs one.
- OpenID Federation Trust between providers established by signed statements rather than by hand.
- Shared signals Events a provider and its applications exchange about a session or an account: CAEP and RISC.
- Verifiable credentials Credentials a user holds and presents: OID4VCI, OID4VP, SD-JWT.
- Session binding Device Bound Session Credentials, and native single sign-on between the applications of one vendor.
- Other authorization models GNAP and UMA 2.0.
- IETF drafts Client ID metadata documents, first-party applications, transaction tokens, identity chaining.
Versions
Each minor version has its own maintenance branch, and until 1.0 the public API may change between minor versions. The versions policy sets the rules, the migration guide lists what a version changes, and the changelog what each one added.