Conformance Runner Suites

Use Case 1: Zero-Config Discovery & Domain Verification Conformance

This workbench runs Use Case 1 (POST /api/conformance/discovery / operationId: runDiscoveryConformance) against a target Producer server using only the generated Producer OpenAPI client (lib/producer-openapi-client.js).


Automated Checks Performed

  1. Unauthenticated MCP Probe (UC1-WWW-AUTHENTICATE-401): Sends postMcpMessage (tools/list) with X-Require-Auth: true and verifies the Producer responds with HTTP 401 Unauthorized and an RFC 9728 WWW-Authenticate: Bearer resource_metadata="..." header.
  2. RFC 9728 Protected Resource Metadata (UC1-RFC9728-PRM-ROOT, PATH, SUFFIX): Invokes getProtectedResourceMetadataRoot, getProtectedResourceMetadataPath, and getProtectedResourceMetadataSuffix and validates ProtectedResourceMetadata (resource, authorization_servers[], scopes_supported[]).
  3. RFC 8414 & OpenID Connect Discovery (UC1-RFC8414-AUTH-SERVER-METADATA, UC1-OIDC-CONFIGURATION): Invokes getAuthorizationServerMetadata and getOpenIdConfiguration, verifying code_challenge_methods_supported includes "S256", token_endpoint_auth_methods_supported includes "private_key_jwt", and client_id_metadata_document_supported: true.
  4. Producer Public JWKS (UC1-PRODUCER-JWKS): Invokes getProducerJwks and validates JsonWebKeySet.
  5. Domain Ownership Verification (UC1-DOMAIN-VERIFICATION-200): Invokes getDomainVerification (/.well-known/google-connected-apps) and verifies HTTP 200 OK without 3xx redirects.

1. Run Discovery Conformance Suite

Configure the target Producer Base URL and run all Use Case 1 checks.