2FA conflict with Dashlane

  • Resolved mmillar2099

    (@mmillar2099)


    5 years, 6 months ago

    Hi,

    I’ve been using 2FA on my website using another plugin (and it worked fine). I’ve just switched to using the Wordfence 2FA option. But I’m having a problem with another password program called Dashlane. Dashlane fills in the login and password fields automatically. In the previous 2FA program it would fill in the login and password page, then I’d move to the next page where I would fill in the 2FA field. With Wordfence, when I move to the 2FA page Dashlane now fills in my password (and it is visible). I think (though I’m not 100% sure) that Wordfence is tagging the 2FA field as a password field, or is tagging it wrong in some way, which leads Dashlane to think it is a password and tries to fill it in. This didn’t happen with the previous 2FA program.

    Thanks

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hey @mmillar2099,

    My apologies for the delayed response with this. I’ve been spending today looking for any threads we may have looked over.

    I’ve spoken with the developer about this. He mentioned our DOM object for the 2FA token field is <input type="text" name="wfls-token" id="wfls-token" aria-describedby="wfls-token-error" class="input" value="" size="6" autocomplete="off"/>, which is the correct markup for this. So unfortunately, I believe the issue may be on the Dashlane side or possbily the browser you’re using.

    Please let us know if anything else comes up.

    Thanks,

    Gerroald

    Thread Starter mmillar2099

    (@mmillar2099)

    Hi, I reported this to Dashlane as well. It does work correctly for the plugin ‘Two Factor Authentication’. I’ve had to turn off 2FA with Wordfence and return to my old plugin.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘2FA conflict with Dashlane’ is closed to new replies.

Tags