COconductorone
MCP Servers

Discover Oidc Endpoints

Changed on

DiscoverOIDCEndpoints fetches the OpenID Connect discovery document for an issuer and returns the authorization, token, and supported scopes.

post/api/v1/mcp_servers/discover_oidc

Request

  • Base URL
    https://example.conductor.one
  • URL
    https://example.conductor.one/api/v1/mcp_servers/discover_oidc
  • Auth
    HTTP bearer and OAuth 2
    Client credentials
    Token URL: /auth/v1/token

Request body

issuerUrlstring

The issuer URL (e.g. "https://accounts.google.com"). The server appends /.well-known/openid-configuration to this URL.

Response

MCPServerServiceDiscoverOIDCEndpointsResponse returns the discovered OAuth2 endpoints.

authorizationEndpointstring

The authorization endpoint URL.

codeChallengeMethodsSupportedstring[] nullable

PKCE code challenge methods supported by the authorization server (RFC 8414). Typical values: "plain", "S256". Empty when the discovery doc omits this field. The frontend should pass the array back unchanged on save so the backend can persist it on the connector and skip per-flow re-discovery.

scopesSupportedstring[] nullable

Scopes supported by the authorization server.

tokenEndpointstring

The token endpoint URL.

Changes