You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
MSC 1467 has just been merged, which allows servers to specify how clients should handle 401's with regards to keeping or deleting encryption keys.
Synapse should implement a mechanism for soft logging out devices or users via the admin API. We may also want to consider what other circumstances we should use soft logout, e.g. unrecognised access tokens, deleting devices, etc
The text was updated successfully, but these errors were encountered:
Possibly we need an administrative way of triggering an expiry, but that can be done by poking things into the database, so I'm declaring that to be a separate feature, and calling this fixed by #5660.
MSC 1467 has just been merged, which allows servers to specify how clients should handle 401's with regards to keeping or deleting encryption keys.
Synapse should implement a mechanism for soft logging out devices or users via the admin API. We may also want to consider what other circumstances we should use soft logout, e.g. unrecognised access tokens, deleting devices, etc
The text was updated successfully, but these errors were encountered: