Can't login through SAML since updating to 4.1.0 when two factor auth is activated

Description:

When two factor authentication is enabled, I can't login through SAML. When I try to, I get back to the login page of rocket chat

Steps to reproduce:

1. Enable Two factor authentication (administation -> accounts -> two factor authentication)
2. log out and go to the login page
3. click on "SAML" of whatever you labled the button and put in your credentials

Expected behavior:

I'm being redirected back to rocket chat and being asked for the authentication code that I got via mail

Actual behavior:

I'm being redirected back to recket chat's login page without being logged in. I get the mail with the authentication code, though.

Server Setup Information:

• Version of Rocket.Chat Server: 4.1.0
• Operating System: Ubuntu Server 18.04
• Deployment Method: docker
• Number of Running Instances: 1
• DB Replicaset Oplog: wiredTiger (oplog Enabled)
• NodeJS Version: 12.22.1
• MongoDB Version: 4.2.17

Client Setup Information

I reproduced the issue on the Android app, Firefox Android, Firefox on Windows and Linux and Vivaldi on Windows and Linux

Additional context

It worked on 4.0.4. Not sure about 4.0.5

Btw. for me the solution is to just disable two factor as it doesn't make sense in the first place. I login via my google account and get the authentication mail to the very same google account. But I guess for people with different setups it could be a problem

To setup SAML i used this tutorial: https://blog.jarrousse.org/setting-up-saml-for-rocker-chat-with-g-suite/

Relevant logs:

No applicable server logs.

Client:

Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 2 background.js:2455
Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 2 background.js:2455
Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 2 background.js:2455
Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 2 background.js:2455
Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 2 background.js:2455
Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 2 background.js:2455
NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIDocShell.domWindow] browsing-context.js:391
Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 2 background.js:2455
NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIDocShell.domWindow] browsing-context.js:391

No source files or tests are named. First reproduce the SAML login with two-factor authentication on 4.1.0, then compare the flow with 4.0.4 and inspect the authentication redirect and code-verification path. Done means a successful SAML login reaches the two-factor code prompt and completes sign-in.