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 Mar 15, 2024. It is now read-only.
Hi @SergeantConfused , this is expected behavior, just as if you changed your own master password, your other active sessions would remain in-tact and able to decrypt the data in local storage in that client's vault, which can be locked and unlocked without trips to the server. The only time that's invalidated is when the access token expires and there's another trip to the server/API. This behavior has also saved many a person's hide when they've lost their MP or changed it w/o realizing and got locked out, but they still had another client logged in they were able to recover and export from before losing everything.
Just got news that I am only halfway correct and mostly wrong...
from SergeantConfused:
When I changed the master password through the Takeover flow, the extensions stayed logged in more than 90 minutes. When I changed the password through the standard change password flow, the same extensions logged out within 1 minute.
Hi @SergeantConfused,
We're cleaning up our repositories in preparation for a major reorganization. Issues from last year will be marked as stale and closed after two weeks. If you still need help, comment to let us know and we'll look into it.
Thanks!
Describe the Bug
When you take over another Bitwarden account as the emergency contact and change the master password, other sessions remain logged-in.
Steps To Reproduce
Expected Result
To be logged out of the session in the other tab/browser.
Actual Result
You remain logged-in. Browser extensions remain logged-in and display an error.
Screenshots or Videos
Environment
Additional Context
N/A.
The text was updated successfully, but these errors were encountered: