Forum Discussion

hexblot's avatar
hexblot
New Contributor
2 months ago

Importing from dashlane does not properly parse OTP

Hello,

it seems that when importing from Dashlane, all items that had OTP not have a generic field (under "other fields") with an OTP url ( otpauth://totp/somesite.net:hexblot@somewhere.com?secret=ABCDEFG01234 ).

Copying the "secret" argument and adding it to a new OTP field works fine, but it's a pain -- and it does not show from the Chrome plugin ( need to edit the item to discover if that field is available )

I do think it's something that seems simple enough to be handled during import instead. 

1 Reply

  • Hello hexblot​! 👋

    I'm sorry for the delay in replying. I've reproduced the same issue on my end when using the Dashlane importer on our website. Oddly enough, the CSV importer on our website is able to import TOTP fields correctly so that might be a workaround for folks who run into the issue going forward until it is fixed.

    I've filed a bug report with our development team so that they can look into this further. Hopefully it can be fixed in the future. 

    -Dave

    #33805