Closed nvhaver closed 3 years ago
Hi I just tried Aegis and Google Authenticator on Android 9 and they worked from the first try. I always used FreeOTP+ without issues.
We are more strict checks for adding TOTP than when logging in (1 interval drift vs 2 intervals drift if I remember correctly). I would check for time differences between your devices because I don't see other reasons.
2FA TOTP is working on older iPhone model, following Tutanota documentation and ensuring all needed software updates are applied.
I was also having the same problem but turned out there was a discrepancy of a few seconds or (maybe 1 minute) between devices, so I just set both to automatically determine the local time and it worked.
We allow for a drift up to a minute in each direction when setting it up and we don't plan to relax it further
After not looking at this issue for over a year, I came back to it to find that everything seems to be working now. I'm able to set up TOTP using Aegis. Not sure whether this is due to an update to Tutanota or Aegis, but I can confirm that the issue is completely resolved and the TOTP works as intended.
Similar issues:
284 (closed after testing of v3.55.6)
1380 (closed as duplicate of #284)
Bug in web app Setting up 2FA does not seem to be working correctly. (Response codes from authenticator are being rejected)
Describe the bug Using the information provided by the Tutanota client, multiple TOTP clients do not seem to be able to correctly set up their TOTP generator.
To Reproduce Steps to reproduce the behavior:
Expected behavior The response code provided in step 4 is accepted.
Desktop:
Smartphone:
Additional context As listed above, similar issues seem to have been fixed in the past. I have verified that my system clock is not out of sync.
The only TOTP client that seems to be able to work with the secrets generated by Tutanota is my KeePassXC's TOTP feature (using 'Default RFC 6238 token settings'). However, as this is where I store my passwords, I am reluctant to include my TOTP there as well (would still be single factor in my opinion). I would prefer using Aegis, as this tool allows me to verify the algorithm parameters after scanning the QR.
During debugging I stumbled upon an issue over on the KeePassXC Github on how they adapted their tool to handle Tutanota's tokens (amoung others). I did check the secret in Aegis after scanning the QR, but it seems to be correct. Perhaps this has something to do with the length of the generated OTP secrets?
Thanks in advance for your time and effort! Keep up the good work.