/usr/ssodata 404

When I launch the lock screen, in the chrome dev tools I can see that the request to path: /user/ssodata is getting a 404. There is an error in the console stating:

There was an error fetching the SSO data. This could simply mean that there was a problem with the network. But, if a “Origin” error has been logged before this warning, please add “https://maypp.auth0.com” to the “Allowed Web Origins” list in the Auth0 dashboard: https://manage.auth0.com/#/clients/asdfasdfasdfasdf/settings.

Is this normal? How do I prevent this request?

1 Like

Getting the same request. Even though this does not seem to affect the usability, would still like to resolve this.

Hey there @shea and @ajv, I would like to find out more about what’s going on here. Could you recreate the work flow and snag us a HAR file and then DM it to me along with your tentant name when you get a chance? I have linked some documentation when troubleshooting with a HAR file. Thanks in advance!

I had forgot to add this to my lock config:

auth: {
  sso: false
1 Like

Sounds great, if you have any questions in the future be sure to let us know!

I also see the 404 if I use “rememberLastLogin: true” in the Hosted lock configuration, and call auth0js’ authorize method with “prompt: true” from my application.

I expected to see the lock with the “Last logged in as” message, but it doesn’t work.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.