From a89be114e961ca786ab969e5bb9cef11d04068f7 Mon Sep 17 00:00:00 2001
From: Thomas Darimont <thomas.darimont@googlemail.com>
Date: Thu, 12 Jun 2025 11:35:44 +0200
Subject: [PATCH] Add link to OIDC discovery specification to the docs.

Fixes #40440

Signed-off-by: Thomas Darimont <thomas.darimont@googlemail.com>
---
 .../guides/securing-apps/partials/oidc/available-endpoints.adoc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/guides/securing-apps/partials/oidc/available-endpoints.adoc b/docs/guides/securing-apps/partials/oidc/available-endpoints.adoc
index dd551d620e6..a18dc3f260c 100644
--- a/docs/guides/securing-apps/partials/oidc/available-endpoints.adoc
+++ b/docs/guides/securing-apps/partials/oidc/available-endpoints.adoc
@@ -69,6 +69,8 @@ The endpoint can also be invoked directly by the application. To invoke this end
 
 The certificate endpoint returns the public keys enabled by the realm, encoded as a JSON Web Key (JWK). Depending on the realm settings, one or more keys can be enabled for verifying tokens. For more information, see the link:{adminguide_link}[{adminguide_name}] and the https://datatracker.ietf.org/doc/html/rfc7517[JSON Web Key specification].
 
+For more details, see the https://openid.net/specs/openid-connect-discovery-1_0.html[OpenID Connect Discovery] specification.
+
 [[_token_introspection_endpoint]]
 ==== Introspection endpoint
 ....