Skip to content

11.0.4

Choose a tag to compare

@aguacongas aguacongas released this 05 Nov 08:04
· 0 commits to 4ab2e86d32b46619565c0b8b0222a336635915bb since this release

11.0.4 (2026-11-05)

Security Fixes

News options are available to control dynamic client registration:

By default, clients created by dynamic registration are protected as follows:

  • A native application using only the authorization_code and refresh_token grant types is a public client: it has no client secret requirement, and PKCE is required.
  • Any other client (web applications, or clients using other grant types such as client_credentials) must authenticate at the token endpoint.
  • PKCE is required for every client using the authorization_code grant type.
  • A web client using the authorization code flow must register https redirect URIs. http is accepted only for loopback hosts (localhost, 127.0.0.1, [::1]).

Web clients using the implicit grant type must still use https redirect URIs and cannot use localhost, and native clients keep their own redirect URI rules.

You can adjust these protections with the following options.

Option Default Description
RequirePkce Always Always: PKCE is required for all clients using the authorization code flow. PublicClientsOnly: PKCE is required only for public clients. Never: PKCE is never required.
RequireClientAuthentication true When false, no client created by dynamic registration is required to authenticate at the token endpoint (all clients are public).
RequireHttpsRedirectUris true When false, web clients using the authorization code flow can register http redirect URIs.
AllowLoopbackHttpRedirectUris true When RequireHttpsRedirectUris is true, accepts http redirect URIs on loopback hosts.
"DynamicClientRegistrationOptions": {
  "RequirePkce": "PublicClientsOnly",
  "RequireClientAuthentication": true,
  "RequireHttpsRedirectUris": true,
  "AllowLoopbackHttpRedirectUris": true
}

The server logs a warning at startup when one of these options is relaxed.

Without PKCE and client authentication, an authorization code intercepted by an attacker can be exchanged with only the client identifier. Keep the default values unless you need to accept clients that can't support them, for example to run a conformance test suite that doesn't send a PKCE code challenge.

These options apply when a client is registered or updated. Clients created before the upgrade keep their settings, check clients created by dynamic registration that have RequirePkce or RequireClientSecret set to false and use the authorization_code grant type.