Skip to content

Enterprise authorization IdP metadata fails strict OIDC discovery #573

Open

Description

@fitchmultz

The IdP document in auth/cross-app-access-complete-flow (0.1.16), now auth/enterprise-managed-authorization on main, omits three required OIDC discovery fields:

  • response_types_supported
  • subject_types_supported
  • id_token_signing_alg_values_supported

A strict client fails discovery before either token exchange. Reproduced with @modelcontextprotocol/client 2.4.0 and the published referee 0.1.16 using the real pi-mcp-adapter driver:

npm exec --yes --package=@modelcontextprotocol/conformance@0.1.16 -- conformance client \
  --command 'bash conformance/driver.sh' \
  --scenario auth/cross-app-access-complete-flow --verbose

The result is CompleteFlowTokenExchange and CompleteFlowJwtBearer failures. A separate driver calling the SDK's discoverAuthorizationServerMetadata(context.idp_issuer) against the same live referee receives HTTP 200, then three Zod invalid_type issues: each named field is expected array, received undefined.

The payload contains only issuer, authorization_endpoint, token_endpoint, jwks_uri, and grant_types_supported. Current source has the same omission. OIDC Discovery §3 requires these fields.

I plan to correct the fixture metadata, keep its ID-token algorithm consistent with its keys, and add a real discovery regression. This does not change client assertions, skip the scenario, or relax client metadata validation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions