Specifications and conformance

The open standards Beffroi implements, grouped by family, and the conformance tools that test them.

OpenID Connect · OAuth 2.0 · FAPI 2.0 · WebAuthn · SAML 2.0

Supported specifications

Five families of specifications. The documentation cites the exact sections implemented; this page gives an overview of each family.

OpenIDConnectSign-in andID tokensDiscovery andthe JWK SetLogout, threewaysClientregistrationOAuth 2.0Grants forapplications,devices andservicesTokens,introspection,revocationFAPI 2.0Requestspushed andsignedTokens boundto the clientBackchannelauthenticationCredentialsPasskeysOne-time andbackup codesPasswords,held to afloorSAML 2.0IdentityproviderServiceproviderMetadata,signature,encryptionBeffroi OP
OpenID ConnectSign-in and ID tokensDiscovery and the JWKSetLogout, three waysClient registrationOAuth 2.0Grants forapplications, devicesand servicesTokens,introspection,revocationFAPI 2.0Requests pushed andsignedTokens bound to theclientBackchannelauthenticationCredentialsPasskeysOne-time and backupcodesPasswords, held to afloorSAML 2.0Identity providerService providerMetadata, signature,encryptionBeffroi OP
Fig. 01 OpenID Connect for the sign-in, OAuth 2.0 for the tokens, FAPI 2.0 for the clients that require the financial-grade profile, the credentials a user holds, and SAML 2.0 in both roles.

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.

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.

Conformance testingThe conformance suite of the OpenID Foundation plays its certification plans against Beffroi every week, in strict mode, and the state of every plan is written in the code repository. SAML has no certification programme: it is judged by xmlsec1 and OpenSSL at every pull request, and by SimpleSAMLphp and Microsoft Entra ID by hand.The conformance suiteof the OpenID Foundation,every week, in strict modeBeffroi OPxmlsec1 and OpenSSLevery signature,at every pull requestSimpleSAMLphp, Entra IDboth SAML roles, by handThe code repositorythe state of every plan
Conformance testingThe conformance suite of the OpenID Foundation plays its certification plans against Beffroi every week, in strict mode, and the state of every plan is written in the code repository. SAML has no certification programme: it is judged by xmlsec1 and OpenSSL at every pull request, and by SimpleSAMLphp and Microsoft Entra ID by hand.Test toolsThe conformance suiteOpenID Foundation,weekly, strict modexmlsec1 and OpenSSLat every pull requestSimpleSAMLphp andMicrosoft Entra IDboth SAML roles,by handBeffroi OPThe code repositorythe state of eachplan
Fig. 02 The conformance suite runs its certification plans against Beffroi every week, and the state of every plan is recorded in the code repository. SAML has no certification programme: xmlsec1 and OpenSSL verify every signature at every pull request, and SimpleSAMLphp and Microsoft Entra ID are tested manually in both roles.
Certification plans run every week
FamilyPlans
OpenID Connect CoreBasic OP, Config OP, Form Post Basic OP
LogoutRP-Initiated Logout OP, Front-Channel Logout OP, Back-Channel Logout OP
FAPI 2.0Security Profile and Message Signing, each with DPoP and with mTLS
FAPI-CIBAPoll, Ping
Registration and keysDynamic 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.

Get started with Beffroi OP.

Features Security