---
title: "GetOpenIdProviderConfig"
method: GET
path: "/.well-known/openid-configuration"
tags: ["OpenID Connect"]
---

# GetOpenIdProviderConfig

`GET /.well-known/openid-configuration`

## Request

- Base URL: `/cdr-register/v1` (relative, and the document was published on a file host, not at the API’s origin)
- URL: `/cdr-register/v1/.well-known/openid-configuration`
- Auth: none declared

Endpoint used by participants to discover the CDR Register OpenID configuration and obtain information needed to interact with it, including its OAuth 2.0 endpoint locations.

## Response `200`

The OpenID Provider Configuration Metadata values

- ResponseOpenIDProviderConfigMetadata: Response containing the Open ID Provider Configuration Metadata
  - `issuer` string, required: URL using the https scheme with no query or fragment component that the CDR Register asserts as its Issuer Identifier
  - `jwks_uri` string, required: URL of the CDR Register's JSON Web Key Set [JWK] document. This contains the signing key(s) used to validate access tokens issued from the CDR Register. Note that this differs from the [JWKS endpoint](https://cdr-register.github.io/register/#getjwks) used to validate SSAs and CDR Register client authentication
  - `token_endpoint` string, required: URL of the CDR Register's OAuth 2.0 Token Endpoint
  - `claims_supported` string[], required: JSON array containing a list of the Claim Names of the Claims that the CDR Register supplies values for
  - `id_token_signing_alg_values_supported` string[], required: JSON array containing a list of the JWS signing algorithms (alg values) supported by the CDR Register for the ID Token to encode the Claims in a JWT. Given the CDR Register does not issue ID tokens, this field can be safely ignored
  - `subject_types_supported` string[], required: JSON array containing a list of the Subject Identifier types that the CDR Register supports. Given the CDR Register does not issue ID tokens, this field can be safely ignored
  - `code_challenge_methods_supported` string[], required: JSON array containing a list of Proof Key for Code Exchange (PKCE) [RFC7636] code challenge methods supported by this authorization server. Given the CDR Register does not support PKCE, this field can be safely ignored
  - `scopes_supported` string[], required: JSON array containing a list of the OAuth 2.0 [RFC6749] scope values that the CDR Register supports
  - `response_types_supported` string[], required: JSON array containing a list of the OAuth 2.0 response_type values that the CDR Registrer supports
  - `grant_types_supported` string[], required: JSON array containing a list of the OAuth 2.0 Grant Type values that the CDR Register supports
  - `token_endpoint_auth_methods_supported` string[], required: JSON array containing a list of Client Authentication methods supported by this Token Endpoint
  - `tls_client_certificate_bound_access_tokens` boolean, required: Boolean value indicating server support for mutual TLS client certificate bound access tokens
  - `request_object_signing_alg_values_supported` string[], required: JSON array containing a list of the JWS signing algorithms (alg values) supported by the CDR Register for Request Objects.

## Changes

- **2026-07-17** `d9372f7f0091`: 1 info
  - endpoint added
- **2019-06-11** `46a7751db141`: 1 breaking
  - api path removed without deprecation

[Operation history](https://skmtc.dev/gov/apis/consumer-data-right-cdr-register-participant-discovery-apis/changes/.well-known/openid-configuration/get.md)

---

[API](https://skmtc.dev/gov/apis/consumer-data-right-cdr-register-participant-discovery-apis.md) - [All operations](https://skmtc.dev/gov/apis/consumer-data-right-cdr-register-participant-discovery-apis/llms.txt) - [OpenAPI document](https://skmtc.dev/gov/apis/consumer-data-right-cdr-register-participant-discovery-apis/revisions/d9372f7f0091?raw)
