Skip to content

Auto-Type: Stale {TOTP} after {DELAY} #12682

@TheUglyOne

Description

@TheUglyOne

Have you searched for an existing issue?

  • Yes, I tried searching and reviewed the pinned issues

Brief Summary

When Auto-Typing, if the {TOTP} value rolls over during a {DELAY} period, then the old {TOTP} value is typed instead of the current value.

(Ideally, services wouldn't take so long to load their TOTP entry form or would accept a slightly stale code, but such is life.)

Steps to Reproduce

  1. Create an entry that includes TOTP.
  2. Set the Auto-Type sequence to {DELAY 9000}{TOTP}.
  3. With less than 9 seconds remaining before the TOTP code rolls over, trigger the Auto-Type.

Expected Versus Actual Behavior

Expected: current {TOTP} value is typed.
Actual: stale {TOTP} value from when Auto-Type was first triggered is typed.

KeePassXC Debug Information

KeePassXC - Version 2.7.10
Revision: b342be4

Qt 5.15.11
Debugging mode is disabled.

Operating system: Windows 10 Version 2009
CPU architecture: x86_64
Kernel: winnt 10.0.19045

Enabled extensions:
- Auto-Type
- Browser Integration
- Passkeys
- SSH Agent
- KeeShare
- YubiKey
- Quick Unlock

Cryptographic libraries:
- Botan 3.1.1

Operating System

Windows

Linux Desktop Environment

None

Linux Windowing System

None

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions