private_key_jwt & Persistent LinkingThis workbench executes Use Cases 2 and 3 (POST /api/conformance/oauth / operationId: runOAuthConformance) against a target Producer server via the generated Producer OpenAPI client.
UC2A-RFC7591-DCR): Calls registerOAuthClient (POST /oauth/register) with the Consumer's /oauth/callback URI and validates the issued client_id and client_secret.private_key_jwt (UC2B-CIMD-PRIVATE-KEY-JWT): Passes the Consumer's /.well-known/oauth-client.json URL as client_id, signs an RS256 client_assertion JWT, and exchanges the authorization code via exchangeOAuthToken while the Producer verifies the Consumer's JWKS.S256) & Persistent Linking (UC3-PERSISTENT-LINKING-NON-ROTATING-REFRESH): Performs an S256 PKCE authorization code exchange followed by 3 sequential grant_type=refresh_token calls using the original refresh_token, verifying that the refresh token remains valid and unrotated.UC3-DETECT-ROTATED-REFRESH-TOKEN-ANTIPATTERN): Sends X-Simulate-Token-Rotation: true on a secondary token and verifies that the conformance suite catches single-use refresh token invalidation (HTTP 400 invalid_grant).UC3-RFC7009-TOKEN-REVOCATION): Invokes revokeOAuthToken (POST /oauth/revoke) and verifies the revoked token can no longer be refreshed.Configure the target Producer Base URL and refresh iterations to execute Use Cases 2 and 3.