From 56745c76aa24c3d358574540b0f011aff6f0b15f Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Tue, 11 Jun 2019 09:22:02 -0600 Subject: [PATCH] Clarify that submit_url being not present only matters for r0.5 --- api/client-server/administrative_contact.yaml | 4 +++- api/client-server/definitions/request_token_response.yaml | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/api/client-server/administrative_contact.yaml b/api/client-server/administrative_contact.yaml index af7cdcd6..c196c109 100644 --- a/api/client-server/administrative_contact.yaml +++ b/api/client-server/administrative_contact.yaml @@ -151,7 +151,9 @@ paths: then be prompted to provide it to the client. If this field is not present, the client can assume that - verification will happen without the client's involvement. + verification will happen without the client's involvement + provided the homeserver advertises this specification version + in the ``/versions`` response (ie: r0.5.0). example: "https://example.org/path/to/submitToken" 403: description: The credentials could not be verified with the identity server. diff --git a/api/client-server/definitions/request_token_response.yaml b/api/client-server/definitions/request_token_response.yaml index bca57227..e47db8a0 100644 --- a/api/client-server/definitions/request_token_response.yaml +++ b/api/client-server/definitions/request_token_response.yaml @@ -30,6 +30,8 @@ properties: prompted to provide it to the client. If this field is not present, the client can assume that verification - will happen without the client's involvement. + will happen without the client's involvement provided the homeserver + advertises this specification version in the ``/versions`` response + (ie: r0.5.0). example: "https://example.org/path/to/submitToken" required: ['sid']