Keepassdx: TOTP not recognized for 'key=...' scheme

[MisterY]

Describe the bug
The OTP is not generated for NextCloud 2FA, scheme is key=BON4U3IICAQTPIXN

To Reproduce

1. Enable TOTP in NextCloud Settings, copy the key.
2. Add an entry in KeePassXC, using the key= + the above key
3. Confirm by generating TOTP and verifying in NextCloud
4. Open the entry in KeePassDX, no OTP field recognized.

Expected behavior
The OTP field recognized and available for copying.

* Keepass Database *

• Created with: complicated. Created a reeeeally long time ago, upgraded protocols and settings over time.
• Version: 2
• Location: Accessed through SAF/pCloud
• Size: 680KB
• Contains attachment: No

KeePassDX (please complete the following information):

• Version: 2.5.0.0beta30
• Build: FDroid
• Language: English

Android (please complete the following information):

• Device: Xiaomi Mi 9T
• Version: 10

Additional context
N/A

[MisterY]

NextCloud settings

[MisterY]

This is most likely provided by this extension
https://apps.nextcloud.com/apps/twofactor_totp

[MisterY]

The same with the Microsoft 2FA.
key=ADQPACX5IKF62NR7&size=6&step=30

[J-Jamet]

Thank you for the feedback. ~indeed, I did not know that this format existed. The problem will be to redo a parser for this format and define the default values~

~Recognized format looks like: otpauth://totp/xxxxx:Username?secret=xxxxxx&period=30&digits=6&issuer=xxxx~
~Identical labels must also be linked. Do you have a documentation that describes this format precisely?~ I had already coded part of this style of keys, but I no longer remembered that it existed ... I will update it and retest it for the next version.

[J-Jamet]

It was only a bad parenthesis in a regular expression! :/ Sorry for that

[MisterY]

Cool! That's good to hear. Will try out with the next build. Thanks!

[MisterY]

Thank you, I can confirm that it works now.