From 00afdeeb0b59a589be64af07b02b44e8ecc16bc2 Mon Sep 17 00:00:00 2001 From: Ricardo Martin Date: Tue, 26 May 2026 12:38:49 +0200 Subject: [PATCH] Use datatracker.ietf.org instead of www.rfc-editor.org for specs Closes #49288 Signed-off-by: rmartinc --- docs/documentation/upgrading/topics/changes/changes-21_1_0.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/upgrading/topics/changes/changes-21_1_0.adoc b/docs/documentation/upgrading/topics/changes/changes-21_1_0.adoc index 1e3ec0ecce5..15197b870b8 100644 --- a/docs/documentation/upgrading/topics/changes/changes-21_1_0.adoc +++ b/docs/documentation/upgrading/topics/changes/changes-21_1_0.adoc @@ -10,7 +10,7 @@ Default `Client ID` mapper of `Service Account Client` has been changed. `Token `client_id` claim is compliant with OAuth2 specifications: - https://datatracker.ietf.org/doc/html/rfc9068#section-2.2[JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens] -- https://www.rfc-editor.org/rfc/rfc7662#section-2.2[OAuth 2.0 Token Introspection] +- https://datatracker.ietf.org/doc/html/rfc7662#section-2.2[OAuth 2.0 Token Introspection] - https://datatracker.ietf.org/doc/html/rfc8693#section-4.3[OAuth 2.0 Token Exchange] `clientId` userSession note still exists.