We upgraded to Lock 11 yesterday. Now we have a problem.
We have a rule written to check for expired passwords.
When we load a page with Auth0 Lock into the browser, that rule immediately fires, even before the user has logged in or even typed anything in the username or password box. The act of loading the page seems to cause Lock to try to authenticate, as if the browser is ‘filling in’ and submitting the login box without the user taking any action. Any idea why this is happening and how do I stop it?
@aalderman Can you share a snippet of your authentication code from Lock 11?
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.