My time is accurate as 2FA works everywhere else. Perhaps its some sort of timing issue where keepassdx thinks the code is valid while codeberg has moved on to the next one. How many codes are valid for login? Only one would be 30 seconds but if 2 codes were valid then that would be a minute. As we already confirmed to be working with Aegis on your machine. If so, there's likely a bug on KeepassDX's side. You might want to try to add the 2FA on KeepassDX and Aegis, to check if the generated 2FA tokens for each period differ. KeePassXC is for people with extremely high demands of secure personal data management. This program requires Microsoft Visual C++ Redistributable to be installed. Click Interfaces and make sure that OTP is checked for both USB and NFC interfaces. As a final step, make sure that apps can talk to your YubiKey. So at a minimum you always got 30 seconds to submit the token, before it becomes "invalid". KeePassXC is a modern, secure, and open-source password manager that stores and manages your most sensitive information. When KeePassium requests your YubiKey, you will need to touch the Y button on the NFC key (or touch the sides of the YubiKey 5Ci key). you can also use the much more modern program KeePassXC instead of KeePass. It would be accepted if you submit that token between 00:30-01:00. KeePass & 2FA: Geht der Authenticator verloren, hilft nur noch ein Back-up. Okay so, Gitea's library allows for previous period and next period, each period is 30 seconds, as an example(using MM:SS): 00:00 00:30 01:00Ĭodeberg's server would always be at the "current" period, so if you submit the previous period, which was generated between 00:00-00:30.
0 Comments
Leave a Reply. |