# Error 404 xml ssodata

**URL:** <https://community.auth0.com/t/error-404-xml-ssodata/16363>\
**Category:** Get Help\
**Created:** [October 5, 2018, 7:10am UTC](https://community.auth0.com/t/error-404-xml-ssodata/16363 "2018-10-05T07:10:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike31](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mike31/32/8666_2.png) [@Mike31](https://community.auth0.com/u/Mike31)\
**Post date:** [October 5, 2018, 7:10am UTC](https://community.auth0.com/t/error-404-xml-ssodata/16363/1 "2018-10-05T07:10:53Z")

</div>

Hi,

I have an error in web browser console when I launch auth0 login page (auth0.js v9) :  
Erreur d’analyse XML : aucun élément trouvé  
Emplacement : https://.eu.auth0.com/user/ssodata  
Numéro de ligne 1, Colonne 1

In network part, I have an 404 error on ssodata because the response is empty.  
It’s not blocking but I don’t know why I have this error and which tenant parameters could be fix this error.  
I specify I do not use Auth0 sso fonctionality.

Thank you

---

<div class="post-metadata">

**Author:** ![nicolas\_sabena](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nicolas_sabena/32/6064_2.png) [@nicolas\_sabena](https://community.auth0.com/u/nicolas_sabena)\
**Post date:** [October 23, 2018, 10:58pm UTC](https://community.auth0.com/t/error-404-xml-ssodata/16363/2 "2018-10-23T22:58:18Z")

</div>

Hi @Mike31.

TL;DR: the `404` from `/user/ssodata` is no cause for concern. Read below for more details.

When a user already has a session in Auth0 and an application requests a new token, Auth0’s Lock used to present a “Last time you logged in as [john.doe@acme.com](mailto:john.doe@acme.com)” button in the hosted login page that would let you reuse the existing session easily (no need to enter credentials again).

New tenants (or existing tenants that turn on “Enable Seamless SSO” in the tenant advanced options) behave differently: if the user already has a session in place then the login step is skipped completely so that the hosted login page is not even displayed (although the user might see other prompts such as MFA or consent).

When this “Seamless SSO” functionality is enabled (which, again, is the default and only behavior available on new tenants) the `/user/ssodata` returns `404`, because its functionality is not really needed anymore.

Lock still tries to call `/user/ssodata` anyway (because Lock, running in the browser, is unaware of the tenant configuration), but when getting a `404` response it simply assumes that there’s no session in place (which is the right assumption to make, because if there was a valid session then the login page would not have been loaded).

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [December 13, 2018, 2:42pm UTC](https://community.auth0.com/t/error-404-xml-ssodata/16363/3 "2018-12-13T14:42:24Z")

</div>

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