You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, I tried searching and reviewed the pinned issues
Brief Summary
According to the otpauth uri format spec the label must not contain a colon, either raw or url encoded. When generating an otpauth uri, keepassxc uses the url encoded entry label as otpauth label, which causes at least some authenticators / parsers to fail parsing.
Steps to Reproduce
Create as password entry containing a colon in its label (for example a website url include http://)
add TOTP settings
get otpauth uri via QR code or secret service integration
Expected Versus Actual Behavior
Colons should probably be sanitized from the label to produce a working uri
KeePassXC Debug Information
Operating System
Linux
Linux Desktop Environment
KDE
Linux Windowing System
X11
The text was updated successfully, but these errors were encountered:
Have you searched for an existing issue?
Brief Summary
According to the otpauth uri format spec the label must not contain a colon, either raw or url encoded. When generating an otpauth uri, keepassxc uses the url encoded entry label as otpauth label, which causes at least some authenticators / parsers to fail parsing.
Steps to Reproduce
Expected Versus Actual Behavior
Colons should probably be sanitized from the label to produce a working uri
KeePassXC Debug Information
Operating System
Linux
Linux Desktop Environment
KDE
Linux Windowing System
X11
The text was updated successfully, but these errors were encountered: