From 6612944f15aa4422c71aec45fd7265e8ed2c167b Mon Sep 17 00:00:00 2001 From: Hugh Nimmo-Smith Date: Wed, 24 Sep 2025 09:37:09 +0100 Subject: [PATCH] Fix description of discovery steps --- proposals/4108-oidc-qr-login.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/proposals/4108-oidc-qr-login.md b/proposals/4108-oidc-qr-login.md index 8432b2ca3..870fc0549 100644 --- a/proposals/4108-oidc-qr-login.md +++ b/proposals/4108-oidc-qr-login.md @@ -1497,9 +1497,10 @@ Before offering this capability it would make sense that the device can check th Where the homeserver is known: -1. Check if the homeserver has a rendezvous session API available (/versions) from this MSC 1. Check that the homeserver is using the OAuth 2.0 API using [server metadata discovery](https://spec.matrix.org/v1.15/client-server-api/#server-metadata-discovery) 1. Check that the Device Authorization Grant is available as per [MSC4341] +1. Check if the homeserver has a rendezvous session API available by attempting a POST to the create rendezvous endpoint + from this MSC. For a new device it would need to know the homeserver ahead of time in order to do these checks.