Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 2
    It seems that this issue is likely one of the following: 1) the TOTP generator is generating TOTP codes based on a time in the past, or 2) the server is invalidating TOTP codes too quickly. To isolate the problem to one of the above, you might want to consider using this TOTP generator in python and modifying it so that it shows not only the TOTP code, but also the time that the TOTP code is based on as well. Commented Apr 23 at 17:21
  • 2
    @mti2935: From what I understand now, the OP actually describes a GUI issue where the authenticator app doesn't always start the counter at 30 seconds but may display the code only for a few seconds -- even when applications typically have a grace period where expired codes are still accepted for some time. If this is indeed the problem, the only solution is to find a more user-friendly authenticator app (or write one yourself). Commented Apr 23 at 18:04
  • Yeah, that seems to be the case. Adjusted the question with a clearly marked EDIT, didn't know that the code would still be valid even after it seemed to timeout in the OTP app. Commented Apr 23 at 21:32
  • 2
    The "Ente Auth" app displays the current code and the next code. So if it's about to switch over you can start typing in the next code and submit it once it becomes the current code. Commented Apr 25 at 5:15