From fbd327a41447ca2a41b827c1fc7893303630d277 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Wed, 18 Jun 2025 10:58:49 +0200 Subject: [PATCH] Add link to server metadata section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Kévin Commaille --- content/client-server-api/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index b582d032..b9c4a7d5 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -1605,8 +1605,8 @@ These are invalid redirect URIs: ##### Dynamic client registration flow To register, the client sends an HTTP `POST` request to the -`registration_endpoint`, which can be found in the server metadata. The body of -the request is the JSON-encoded [`OAuthClientMetadata`](#client-metadata). +`registration_endpoint`, which can be found in the [server metadata](#server-metadata-discovery). +The body of the request is the JSON-encoded [`OAuthClientMetadata`](#client-metadata). For example, the client could send the following registration request: