Lock: Lock's SSO transformation triggers LastPass Chrome extension to autofill repeatedly

Created on 7 Jun 2018  路  8Comments  路  Source: auth0/lock

Lock version: 10
Browser: Chrome (tested on Firefox, the issue does not happen on Firefox)
OS: MacOS

When SSO is enabled, Lock will transform to hide the password field when the user-type email matches a domain configured in Auth0. In addition, It will transform to show the password field again when the user starts deleting characters from the email field (domain becomes not matched).

The problem is, if the user installed LassPass Chrome extension, which autofills the email, every time the user updates the email, Lock's transformation triggers LastPass extension to autofill the email field repeatedly. This causes the user cannot update the email field at all, unless the user hit delete furiously.

Here is an example:

screen shot 2018-06-07 at 12 09 59 pm

LastPass autofills the email, and the domain is matched. The password field is hidden.

screen shot 2018-06-07 at 12 25 51 pm

If the user hit delete, Lock should transform to show the password field as shown in the second image. However, the email is autofilled again. Lock immediately becomes back to the first image.

Most helpful comment

Password managers are weeeeeird :) I just submitted a fix, which should be out in the next release. Thanks for reporting it

All 8 comments

Can you record a video of this? I don't understand what's happening.

A small screen recording can be downloaded here (15MB).

Password managers are weeeeeird :) I just submitted a fix, which should be out in the next release. Thanks for reporting it

Thanks!

May I ask when the next release will be? So that we can arrange our release to apply the fix.

I'm trying to narrow a few extra SSO issues and I to ship everything on Thursday. As always, things might go wrong and dates can change, but those this is the plan right now 馃槵

I just opened the last pr for the SSO issues. I'll cut a new release once both are merged! Thanks for your patience.

Looks like this fix is not in _11.17.2_. Just want to ask approximately when will _11.17.3_ be release, please?

Sorry to keep you waiting. The next release is scheduled to happen this week.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mcrawshaw picture mcrawshaw  路  5Comments

sedubois picture sedubois  路  4Comments

DavidWells picture DavidWells  路  5Comments

juhaelee picture juhaelee  路  3Comments

jeaye picture jeaye  路  5Comments