Specifications and conformance
The open standards Beffroi implements, grouped by family, and the conformance tools that test them.
Supported specifications
Five families of specifications. The documentation cites the exact sections implemented; this page gives an overview of each family.
OpenID Connect
The sign-in of a user, the ID token that identifies them, the discovery document that describes the provider, logout in its three forms, and the dynamic registration of a client that was not declared in advance.
OAuth 2.0
The tokens, and how each kind of caller obtains one: a browser with a code and PKCE, a service with its credentials, a device with no keyboard, a gateway exchanging a token for another. Access tokens of a known type, and the endpoints that introspect and revoke them.
- The framework
- PKCE
- Device authorization
- Token exchange
- JWT access tokens
- Introspection and revocation
- Security best current practice
FAPI 2.0
The profile for high-assurance clients: requests pushed or signed, responses signed, tokens bound to a key or a certificate, and authentication started on one device and approved on another.
Credentials
Passkeys as the W3C defines them, one-time codes from an authenticator application, and passwords held to the minimum the NIST guidelines set. The claims that tell a client how a user authenticated.
SAML 2.0
Web browser single sign-on and single logout over the HTTP-Redirect and HTTP-POST bindings, as identity provider and as service provider. Peers configured from their metadata. Every assertion signed, and encrypted on request, under the XML standards of the W3C.
Every specification, section by section, in the documentation
Conformance testing
The OpenID Foundation conformance suite is open source and runs against Beffroi every week in strict mode, where a warning counts as a failure.
| Family | Plans |
|---|---|
| OpenID Connect Core | Basic OP, Config OP, Form Post Basic OP |
| Logout | RP-Initiated Logout OP, Front-Channel Logout OP, Back-Channel Logout OP |
| FAPI 2.0 | Security Profile and Message Signing, each with DPoP and with mTLS |
| FAPI-CIBA | Poll, Ping |
| Registration and keys | Dynamic OP, Third Party-Init OP, Rotate Keys |
Known failures are listed with their reason and the issue that tracks them. Any other failure, or a known failure that starts passing, fails the run. The OpenID Certified mark is a separate filing with the foundation, announced on the conformance page once it is made.