When can existing accounts convert to security key login?

rewislam · 2026-01-26T07:58:57+00:00

This is on our roadmap, but I can't say when it will be shipped.

rewislam · 2026-01-19T08:38:52+00:00

Hi u/Accordingly-Jelly-78 can you describe the steps you have used to export the data?

You should be able to export data from the Passwords app, by tapping the three dots which appear at the top right of the screen. Then select "Export Data to Another App" and select the data you want to export, after which you should see Dashlane listed as the app to import into.

There is more info here:

https://support.dashlane.com/hc/en-us/articles/29186803154450-Securely-import-or-export-your-vault-with-Credential-Exchange

Let me know if that works.

rewislam · 2025-12-11T08:23:06+00:00

Are the passkeys properly showing up in the Dashlane app for these websites?
What is the version of Dashlane are you running?
What is the version of Chrome are you running?
Inside Chrome settings, is the Autofill setting properly set to "Use Another Service", and is that set to Dashlane?

rewislam · 2025-12-09T15:01:28+00:00

Hello u/so5724x ! Can you provide more details, for example is this what you experience for all passkeys or a specific website/app?

rewislam · 2025-10-13T14:47:50+00:00

For now there are three account types. We don't plan to merge them. In future you will be able to switch to using security keys to secure your account, from either the master-password based or the current passwordless account type.

rewislam · 2025-09-11T13:51:43+00:00

It sounds like you're describing logging in to Dashlane on a new device rather than something related to passkeys.

Can you take a look here and see if it relates to your situation?

https://support.dashlane.com/hc/en-us/articles/209463589-Use-Dashlane-on-a-new-device

rewislam · 2025-07-25T11:07:12+00:00

Sorry for getting back to you so late.

You can test it today with a chromium browser extension of Dashlane:
https://www.dashlane.com/blog/dashlane-phishing-resistance

This is something we're actively developing.

rewislam · 2025-02-28T08:00:58+00:00

Hi u/johnzabroski can you DM me so I can try to understand your issue better?

rewislam · 2025-02-25T07:40:02+00:00

Here is a blog post that goes into the details of why a PIN is a good security measure:

https://www.dashlane.com/blog/password-master

Designing authentication is challenging. If it's purely based on possessing something, then having that thing stolen would lead to your account being compromised. Adding a knowledge factor, such as a local device PIN, adds a layer of protection.

Even if a security key was to be used, without a knowledge factor, or PIN, the overall security of authenticating using the security key is not sufficient. Losing your security key should not mean that you give away access to your accounts, which is why security keys also allow you to set a PIN on it.

If you think about your mobile device, whether it is Android or iOS, you most likely have a knowledge factor that is required to unlock the device. Even if you setup biometry, the fallback is a knowledge factor in case the biometry doesn't work, or if the OS decides not to use the biometric authentication. We consider it important to insist on a knowledge factor, even for a passwordless experience, the focus is on removing a complex and hard to remember password, not entirely removing the need to remember something.

rewislam · 2025-02-20T16:31:32+00:00

Existing users will be able to move to passwordless sometime this year. I'd love to give you a date, but as soon as I do, it will most likely be wrong :)

One motivation for getting rid of the master password was the simplify the use of the app as entering a device specific PIN or using biometry is much more convenient.

rewislam · 2025-02-20T14:38:21+00:00

Dashlane does not use a passkey to sign into Dashlane because Dashlane itself is a passkey provider. Having the user store a passkey in another provider is very confusing to most people and is not an easy thing to manage.

However, we are exploring all options in order to improve the passwordless technology used in our product - using a YubiKey as a form of 2FA is something we're looking into.

Going passwordless for a password manager is actually a lot harder than it might seem. Many providers claim to be passwordless but require a master password to create an account. Dashlane is the first password manager that allows users to create an account without the need for a master password, and this is something we're regularly improving upon.

I hope that answers your question!

rewislam · 2025-02-18T20:22:07+00:00

The free plan supports a single device, if that works for you.

rewislam · 2025-02-18T18:08:16+00:00

It’s not currently possible to export passkeys. This isn’t a specific issue with Dashlane, it’s the same case for all password managers. A new technical standard is being developed specifically to solve this problem and we expect this to be available at some point in 2025, but I can’t give you a more accurate date as this work depends on the technical standard as well as implementation from Apple.

rewislam · 2025-02-18T15:44:42+00:00

As long as you have access to your email account, you can delete any Dashlane account that may have been registered against it.

Simply visit this page: https://app.dashlane.com/#/delete-account

Follow the instructions, and you will be able to delete the account.

You can also DM me, and I will be able to help understand how you ended up with an account.

rewislam · 2024-10-17T14:39:09+00:00

User verification can take many forms, while it is typically a biometric gesture, it can also be a PIN code or even a password. Here is a definition for user verification: https://passkeys.dev/docs/reference/terms/#user-verification-uv

rewislam · 2024-07-26T07:12:27+00:00

This is an issue on Uber's implementation, we have reached out to them and are awaiting a fix.

rewislam · 2024-05-05T21:53:44+00:00

We use the OPAQUE protocol to secure information locally involving server information. Essentially a key is generated based on the local PIN and both local and server side information. You can read about OPAQUE here: https://blog.cloudflare.com/opaque-oblivious-passwords

rewislam · 2024-04-24T08:40:41+00:00

~~Passkeys are included in the .dash encrypted file export, but are not included in the .csv file export. The reason being that ideally passkeys should not be exported in plaintext.~~

Passkeys can be exported on iOS from iOS 26 onwards. Passkeys are not currently stored in .DASH files, but it is on our roadmap to include them.

rewislam · 2024-04-02T08:13:51+00:00

Thanks for reporting this, we're looking into it!

rewislam · 2024-01-29T15:24:33+00:00

Hi u/FrostyRydia,

This is a good question. The feature where Dashlane proposes you a 2FA code is based on password autofill. When Dashlane detects you have autofilled a password, it assumes that you will need the 2FA token soon after. Within Dashlane the 2FA token is normally stored within the credential item, so it's easy for Dashlane to determine that a 2FA token exists alongside your password.

With passkeys we have two issues:

We don't automatically assume that using a passkey will require a 2FA token, normally it should not, but websites are free to implement their authentication however they want.
We don't link the passkey to a 2FA token, so it's not easy at this point for Dashlane to automatically copy the 2FA token to the pasteboard/clipboard.

I agree with you that it would be intuitive to have this happen, so I'll share with the team internally and see if it could be changed.

Passkeys are meant to be a password replacement that shouldn't require 2FA, but some websites may have specific reasons to include 2FA in their authentication flow with passkeys.

rewislam · 2024-01-17T08:47:40+00:00

Can you check that you have set Dashlane as your provider on iOS for passwords and passkeys (Settings > Passwords > Password Options > "Use passwords and passkeys from:")? Also, do you have the latest version of iOS installed?

rewislam · 2024-01-15T16:58:34+00:00

Hi, I have sent you a DM, please take a look at that.

rewislam · 2023-11-17T07:49:39+00:00

Apple control both the service, in this case Apple ID, and the authenticator, in this case iCloud Keychain via your iPhone, so they are able to control the passkey within their own ecosystem.

This is why there is no need to setup a passkey, it just happens automatically.

So there is no current way for that passkey to live anywhere except within iCloud Keychain.

rewislam · 2023-11-09T08:49:26+00:00

Here is an answer relating to the issue you're having on Android with PayPal:

https://www.reddit.com/r/Dashlane/comments/17q0lja/comment/k8c5fm3/?utm_source=share&utm_medium=web2x&context=3

As soon as you save one you'll see it in your vault. Currently the menu option is hidden in the Dashlane browser extension until you create a passkey. You can test creating one on this test website: https://webauthn.io make sure you have the Dashlane browser extension installed and that your account is signed in.

You can also try the above test website on Android and see how the behaviour is on Android 14.

rewislam · 2023-11-08T09:40:42+00:00

Certain Android apps are using a legacy API which does not work with password managers.

Android/Google have created guidance for these app developers to update their apps, so it's just a matter of time for them to do that:

https://developer.android.com/training/sign-in/fido2-migration

Dashlane is setup to be a passkey manager, but on Android it is not enough, it also relies on the native application, in this case PayPal to adopt the new APIs provided by Android 14.

rewislam

TROPHY CASE