Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-08-05 07:27:52 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Fix conflicting information on requirement of fragment response mode

Browse source
This commit is contained in:
Tulir Asokan 2026-08-02 20:07:58 +03:00
parent d0ba2aaef8
commit aa9439454b
2 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
changelogs/client_server/newsfragments/2430.clarification Normal file
View file

@ -0,0 +1 @@
Fixed conflicting information on whether clients using the authorisation code grant are required to use the `fragment` response mode.

6
content/client-server-api/_index.md
View file

@ -2409,9 +2409,9 @@ To use this grant, homeservers and clients MUST:
- 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](#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.
Clients with an HTTPS redirect URI SHOULD 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).
##### Device authorisation grant