Carey Bishop

Thanks @dreichl, that snapshot build works the way I was expecting.

No, I don't think that's helpful. I already have the information in the Bitwarden JSON file format, the trouble is that KeePass doesn't import this into the right fields (TimeOtp-*). The patch I provided above can be applied to KeePass to resolve the issue. You can find information about the Bitwarden JSON file format including a link to a sample file at https://bitwarden.com/help/condition-bitwarden-import/#condition-a-json The totp field in that file already contains the information that I'm interested...

Hi there I've been trying to import some Bitwarden JSON containing TOTP information into KeePass, and I noticed that it appears to just create a custom field called TOTP, instead of importing the TOTP information into the separate fields that KeePass expects. As such, it's not possible to generate TOTP codes from the imported entries. I've had a look at the code and I've come up with a simple patch to the ImportLogin method in BitwardenJson112.cs. The new code checks to see if the TOTP data being...