From 870cded27cd623e5f212feea02d7b77e9c56fe00 Mon Sep 17 00:00:00 2001 From: Quentin Gliech Date: Thu, 20 May 2021 12:10:13 +0200 Subject: [PATCH] MSC2918: account registration API changes --- proposals/2918-refreshtokens.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/proposals/2918-refreshtokens.md b/proposals/2918-refreshtokens.md index f68964c308b..e6c0639d968 100644 --- a/proposals/2918-refreshtokens.md +++ b/proposals/2918-refreshtokens.md @@ -18,6 +18,14 @@ The login API returns two additional fields: - `expires_in_ms`: The lifetime in milliseconds of the access token. - `refresh_token`: The refresh token, which can be used to obtain new access tokens. + +### Account registration API changes + +Unless `inhibit_login` is `true`, the account registration API returns two additional fields: + +- `expires_in_ms`: The lifetime in milliseconds of the access token. +- `refresh_token`: The refresh token, which can be used to obtain new access tokens. + ### Token refresh API This API lets the client refresh the access token. @@ -45,7 +53,7 @@ response: ### Device handling The current spec states that "Matrix servers should record which device each access token is assigned to". -This must be updated to reflect that devices are bound to a session, which are created during login and stays the same one after refreshing the token. +This must be updated to reflect that devices are bound to a session, which are created during login and stays the same after refreshing the token. ## Potential issues