We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
On iOS, Keepassium is saving TOTP in this format:
otpauth://totp?secret=ABCDEFGHIJK&period=30&digits=6&algorithm=SHA1
If I open the database in keepassDX, there are no TOTP codes generated. On keepassXC, working good.
In DX, TOTP is saved like this:
otpauth://totp/None%3AOTP?secret=ABCDEFGHIJK&period=30&digits=6&issuer=None&algorithm=SHA1
Maybe DX can't read the keepassium format? Otherwise I don't know why DX doesn't generate the codes.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Show TOTP codes. (KeepassXC can)
KeePass Database
KeePassDX:
Android:
The text was updated successfully, but these errors were encountered:
fix: regex OTP recognition #1596
815fb91
Fixed in 4.0.3
Sorry, something went wrong.
No branches or pull requests
Describe the bug
On iOS, Keepassium is saving TOTP in this format:
otpauth://totp?secret=ABCDEFGHIJK&period=30&digits=6&algorithm=SHA1
If I open the database in keepassDX, there are no TOTP codes generated. On keepassXC, working good.
In DX, TOTP is saved like this:
otpauth://totp/None%3AOTP?secret=ABCDEFGHIJK&period=30&digits=6&issuer=None&algorithm=SHA1
Maybe DX can't read the keepassium format? Otherwise I don't know why DX doesn't generate the codes.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Show TOTP codes. (KeepassXC can)
KeePass Database
KeePassDX:
Android:
The text was updated successfully, but these errors were encountered: