-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSO doesnt appear to Work with 2FA (TOTP) #2703
Comments
Can you try on Experimental app from TestFlight? |
unfortunatly i have no capacity, but will check with next release. will close and reopen if #2683 wasnt the fix. |
Here i am with iOS 4.13.1. TOTP + SAML still sending me back to SAML. For a brief moment the OTP field was displayed. Want me to provide a video or so? |
@b90g Yes, please. |
Video.21-01-19.08-17-52.0956.mp4The first video shows SAML SSO with 2FA activated. I only press the yellow sign in button once and after rocketchat is for a while at the login screen i press the pink login button again which shows that SAML recognized me from my earlier login attempt. inbetween the first and the second video i disabled the 2fa, it shows that i login with the same SAML-session: Video.21-01-19.08-18-25.0957.mp4 |
Thanks.
That's expected. When you login via any 3rd party login (OAuth, SSO), the webview keeps you connected in the same session. |
With email 2FA users have the same behaviour, want me to open another issue for that? |
We are seeing this behavior with RC iOS client 4.15.0.23394 (server version is currently 3.12.3) when TOTP 2FA is enabled, along with Custom Oauth provider. Clearing up cookies did not help. |
Fixed on #2978 |
Confirming working in iOS client 4.16.1.23838. |
Description:
Same as mentioned here #2284 but with time based codes.
Environment Information:
Steps to reproduce:
2.1 SAML works,
2.2 then back to SAML... loop
Expected behavior:
Getting asked the time based code.
Actual behavior:
getting back to the SAML login in a loop
Additional context:
its similar maybe the same as the earlier references FIDO issue.. maybe..
The text was updated successfully, but these errors were encountered: