From 5572d33453cf27896e4e78c435bb6e7c200d2c05 Mon Sep 17 00:00:00 2001
From: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
Date: Tue, 16 Aug 2022 18:12:10 +0100
Subject: [PATCH] Require `access_token`, `device_id` and `user_id` fields in
 `/login` response (#1210)

---
 changelogs/client_server/newsfragments/1210.clarification | 1 +
 data/api/client-server/login.yaml                         | 1 +
 2 files changed, 2 insertions(+)
 create mode 100644 changelogs/client_server/newsfragments/1210.clarification

diff --git a/changelogs/client_server/newsfragments/1210.clarification b/changelogs/client_server/newsfragments/1210.clarification
new file mode 100644
index 00000000000..6a02485256e
--- /dev/null
+++ b/changelogs/client_server/newsfragments/1210.clarification
@@ -0,0 +1 @@
+Clarify that the "device_id", "user_id" and "access_token" fields are required in the response body of `POST /_matrix/client/v3/login`.
\ No newline at end of file
diff --git a/data/api/client-server/login.yaml b/data/api/client-server/login.yaml
index d279445d823..4c348fcd980 100644
--- a/data/api/client-server/login.yaml
+++ b/data/api/client-server/login.yaml
@@ -210,6 +210,7 @@ paths:
                   form as the one returned from .well-known autodiscovery.
                 allOf:
                   - "$ref": "definitions/wellknown/full.yaml"
+            required: ["access_token", "device_id", "user_id"]
         400:
           description: |-
             Part of the request was invalid. For example, the login type may not be recognised.