From 3a1479a48b2dd78cb9e0605167c627ef771680fc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Wed, 18 Jun 2025 11:14:41 +0200 Subject: [PATCH] Add link to client registration 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 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index 714868f3..a02af2fd 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -1776,7 +1776,7 @@ To use this grant, homeservers and clients MUST: - Support the authorization code grant as per [RFC 6749 section 4.1](https://datatracker.ietf.org/doc/html/rfc6749#section-4.1). - Support the [refresh token grant](#refresh-token-grant). - Support PKCE using the `S256` code challenge method as per [RFC 7636](https://datatracker.ietf.org/doc/html/rfc7636). -- Use pre-registered, strict redirect URIs. +- Use [pre-registered](#client-registration), strict redirect URIs. - Use the `fragment` response mode as per [OAuth 2.0 Multiple Response Type Encoding Practices](https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html) for clients with an HTTPS redirect URI.