From a10802daecacbe1cc53c80d01a39df8ae31f9e8f Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Wed, 3 Apr 2024 15:22:40 -0600 Subject: [PATCH] Update proposals/3939-account-locking.md Co-authored-by: Hubert Chathi --- proposals/3939-account-locking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/3939-account-locking.md b/proposals/3939-account-locking.md index 3b6d1594..85c7af27 100644 --- a/proposals/3939-account-locking.md +++ b/proposals/3939-account-locking.md @@ -52,7 +52,7 @@ Locked accounts are still permitted to access the following API endpoints: * [`POST /logout`](https://spec.matrix.org/v1.9/client-server-api/#post_matrixclientv3logout) * [`POST /logout/all`](https://spec.matrix.org/v1.9/client-server-api/#post_matrixclientv3logoutall) -Servers SHOULD NOT invalidate an account's access tokens in case the account becomes +When a user's account is locked, servers SHOULD NOT invalidate an account's access tokens in case the account becomes unlocked: the user should be able to retain their sessions without having to log back in. However, if a client requests a logout (using the above endpoints), the associated access tokens should be invalidated as normal.