We are experiencing the exact same problem. We created a new tenant and a new client in order to separate our Dev/Test/Production environments.
Configuration steps:
Client Type : Regular Web Application
Token Endpoint : Post
Allowed Callback URLs: http://localhost:8080/mycallback
We used the default hosted page template. When you sign-up a new user , the user appears under users on the Auth0 portal , there are no errors under logs but Lock displays a “WE’RE SORRY, SOMETHING WENT WRONG WHEN ATTEMPTING TO LOG IN.”
We also noticed that in the webrequest https://mydomain.auth0.com/usernamepassword/login the response comes back as :
{“statusCode”:403,“description”:“Invalid state”,“name”:“AnomalyDetected”,“code”:“access_denied”}
I must add that hosted pages works in our old dev tenant which was created sometime in 2017 when Lock was still in version 10.2.2 .,We are experiencing the exact same problem. We created a new tenant and a new client in order to separate our Dev/Test/Production environments.
Configuration steps:
Client Type : Regular Web Application
Token Endpoint : Post
Allowed Callback URLs: http://localhost:8080/mycallback
We used the default hosted page template. When you sign-up a new user , the user appears under users on the Auth0 portal , there are no errors under logs but Lock displays a “WE’RE SORRY, SOMETHING WENT WRONG WHEN ATTEMPTING TO LOG IN.”
We also noticed that in the webrequest https://mydomain.auth0.com/usernamepassword/login the response comes back as :
{“statusCode”:403,“description”:“Invalid state”,“name”:“AnomalyDetected”,“code”:“access_denied”}
I must add that hosted pages works in our old dev tenant which was created before sometime in 2017 when Lock was still in version 10.2.2 .