Skip to main content

OIDC conformance

The provider has two complementary test layers. Repository tests exercise the complete authorization-code and refresh-token state machine on every CI run. The OpenID Foundation Conformance Suite validates the public discovery and JWKS surface of the deployed test environment.

Repository coverage​

tests/oidc-provider.test.ts covers the successful Authorization Code flow with PKCE and the protocol failures required by the provider test plan:

ScenarioExpected result
Valid code, exact redirect URI, client and S256 verifieraccess, ID and refresh tokens are issued
Authorization code reused after a successful exchangeinvalid_grant
Authorization code exchanged after 60 secondsinvalid_grant
Different loopback port or other redirect URIinvalid_grant
Wrong PKCE verifierinvalid_grant
Different client IDinvalid_grant
Spent refresh token outside the 10-second desktop retry windowinvalid_grant and family revocation
Spent refresh token replayed more than once inside the retry windowinvalid_grant and family revocation

The same test signs a token with the current key, proves that it still verifies while that key is previous and present in JWKS, rotates again, and proves that verification fails once the original key is retired and removed from JWKS. tests/oidc-signing-keys.test.ts independently checks the same overlap rule against the key-state model.

Both files match the tests/**/*.test.ts model-test glob. The GitHub Actions unit job runs npm run test:models on every push and pull request, so the provider matrix and rotation assertions are CI gates rather than manual checks.

OpenID Foundation profile run​

The Config OP certification profile was run on 4 September 2026 against:

https://sabrobotix-suite-test.sab-group.workers.dev/.well-known/openid-configuration

That historical Worker URL was retired on 23 October 2026. The retained report records the original target; new runs must use the Oracle test URL below.

The run used OpenID Foundation Conformance Suite 5.2.4, revision 9be6de8 (full revision 9be6de851add879d32152ba4731da16db33a575a). The test module was oidcc-discovery-endpoint-verification with server_metadata=discovery and client_registration=static_client.

The first run recorded 32 successful checks, six informational entries, and one failure:

OIDCCCheckDiscEndpointIdTokenSigningAlgValuesSupported
RS256 support is required, but the server does not list it in
id_token_signing_alg_values_supported

This was a real certification gap and not a test-harness error: changing only the advertised metadata would have been incorrect. Issue #44 added RSA signing, made RS256 the default, and retained verification through the previous ES256 key during the one-rotation overlap.

The profile was rerun after migration 0009_oidc_rs256.sql and deployment to test. Run JuzRwXCEs3C29I7, started at 2026-09-04T07:49:43Z, finished PASSED with 33 successful checks, six informational entries, and no failure or warning. OIDCCCheckDiscEndpointIdTokenSigningAlgValuesSupported observed ["RS256", "ES256"] and satisfied requirement OIDCD-3.

The evaluated areas passed, including HTTP status and JSON content type, issuer/discovery consistency, metadata schema, response and grant types, subject type, HTTPS endpoints, JWKS retrieval and structure, absence of private key material, scopes, claims, and PKCE metadata. Registration endpoint, signed-UserInfo metadata, request objects, and the claims request parameter are unsupported optional features and were reported as informational skips.

A machine-readable summary of this execution is kept with the documentation: Config OP result.

Re-running the profile​

Use the current official openid/conformance-suite image in development mode, create an oidcc-config-certification-test-plan with the current Oracle test discovery URL, https://suite-test.sabrobotix.com/.well-known/openid-configuration, and run its single oidcc-discovery-endpoint-verification module. Record the suite version and revision from /api/server because certification rules and diagnostics can change between releases. Never run the profile against production unless that target has been explicitly approved.

The local suite exposes its API without a token in development mode. After cloning the suite, the complete non-interactive run is:

docker compose -f docker-compose-prebuilt.yml up -d

oidc_suite_url="https://localhost.emobix.co.uk:8443"
discovery_url="https://suite-test.sabrobotix.com/.well-known/openid-configuration"

curl -kfsS -X POST \
"$oidc_suite_url/api/plan?planName=oidcc-config-certification-test-plan" \
-H 'Content-Type: application/json' \
--data "{\"server\":{\"discoveryUrl\":\"$discovery_url\"}}" \
> oidc-plan.json

plan_id="$(jq -r .id oidc-plan.json)"
curl -kfsS -X POST \
"$oidc_suite_url/api/runner?test=oidcc-discovery-endpoint-verification&plan=$plan_id" \
> oidc-run.json

run_id="$(jq -r .id oidc-run.json)"
curl -kfsS "$oidc_suite_url/api/info/$run_id" | jq .
curl -kfsS "$oidc_suite_url/api/log/$run_id" | jq \
'[.[] | select(.result == "FAILURE" or .result == "WARNING")]'