Skip to content

OpenID Connect Certification Scope

Product

OpenIdentityStack

Certification Type

OpenID Provider

Initial Certification Profiles

  • OpenID Connect Core Basic OP
  • Discovery-based OP configuration
  • Authorization Code Flow
  • PKCE
  • Static client registration

Deferred Profiles

  • Dynamic Client Registration
  • Implicit Flow
  • Hybrid Flow
  • Logout profiles
  • FAPI
  • OpenID Federation
  • eKYC / Identity Assurance
  • Request Objects (JAR) — see below

Request Objects (JAR)

Request objects are not supported. An authorization request carrying a request parameter is rejected with error=request_not_supported.

No protocol parameter inside the object is honoured. The signature is not verified, the object is not merged into the request, and redirect_uri, response_type, scope and the rest are read from the query string only. The one exception is deliberate and narrow: to build a spec-conformant error response the OP Base64URL-decodes the payload and reads state, and nothing else, when the query string omits it. That decode is unauthenticated attacker-controlled input, so it is failure-tolerant by construction — a malformed segment, invalid JSON, or a non-string state yields no value rather than an error, and the value is only ever echoed back to an already-validated redirect_uri.

How the error reaches the client therefore depends on the outer query string:

  • Outer redirect_uri present and registered for the client — the error is redirected there with error, error_description and state, as OpenID Connect Core §3.1.2.6 prescribes.
  • Outer redirect_uri absent, or present but not registered — no redirect is issued and the error is rendered on the authorization endpoint. This is required, not a shortfall: §3.1.2.6 forbids redirecting to an unvalidated URI, and a redirect_uri carried only inside the request object is never processed, so it has not been validated.

Rejection is an explicitly permitted posture for the Basic OP profile. oidcc-unsigned-request-object-supported-correctly-or-rejected-as-unsupported ends SKIPPED when the capability is not advertised. oidcc-ensure-request-object-with-redirect-uri sends an unregistered outer redirect_uri, so it exercises the second case above. It is one of the modules that pauses for an operator rather than reaching a machine verdict, and its REVIEW ceiling is by design — see run-oidf-conformance-suite.md.

Discovery is therefore deliberately silent on request_object_signing_alg_values_supported. Advertising a capability the OP does not implement is a worse failure than advertising nothing: relying parties would build against a signalled feature that never works, and discovery metadata is precisely what the Config OP plan certifies. OpenIddict 7.6 provides no server-side request-object support to enable, so implementing JAR would mean hand-writing the parse, signature verification, iss/aud binding, algorithm-confusion and replay defences — work that belongs with the deferred FAPI profile, not with Basic OP certification.

Certification Environment

The certification environment is a dedicated public deployment of OpenIdentityStack used only for OpenID Foundation conformance testing.

The public issuer URL is intentionally environment-specific and is managed in private operational deployment assets outside this repository.

https://<public-issuer-host>/

Certification Claim

The project must not display the OpenID Certified mark until certification has been approved by the OpenID Foundation.

Until then, use this wording:

OpenIdentityStack is designed to implement OpenID Connect using OpenIddict and is being prepared for OpenID Provider certification.