Description:

user is not logged out completely after reset E2E keys, they have to sign in again to get their new E2E keys. thus all the requests after reset E2E keys are unauthorized, the user is not pushed to the home route to sign in again.

Steps to reproduce:

1. Go to My account
2. navigate to security, E2E Encryption
3. click the Reset E2E key

Expected behavior:

user must be logged out so that a new key will be generated after they sign in again

Actual behavior:

Server Setup Information:

• Version of Rocket.Chat Server: 3.13.0-develop
• Operating System: Linux
• Deployment Method: tar
• Number of Running Instances: 1
• DB Replicaset Oplog: enabled
• NodeJS Version: 12.18.4 - x64
• MongoDB Version: 4.2.8

Client Setup Information

• Desktop App or Browser Version: 88.0.4324.182
• Operating System: Ubuntu 20.04

Additional context

Relevant logs: