# Get last login not working

**URL:** <https://community.auth0.com/t/get-last-login-not-working/17084>\
**Category:** Get Help\
**Tags:** remember-last-login, sso, lock\
**Created:** [October 23, 2018, 6:28am UTC](https://community.auth0.com/t/get-last-login-not-working/17084 "2018-10-23T06:28:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![luisguerra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/luisguerra/32/4981_2.png) [@luisguerra](https://community.auth0.com/u/luisguerra)\
**Post date:** [October 23, 2018, 6:28am UTC](https://community.auth0.com/t/get-last-login-not-working/17084/1 "2018-10-23T06:28:50Z")

</div>

Hi

I configured a Single Page Application for a brand new project in Angular 6

I want to enable the one-click login, by setting the rememberLastLogin flag to `true` by following this rules [Lock Configuration Options - Auth0 Docs](https://auth0.com/docs/libraries/lock/v11/configuration#rememberlastlogin-boolean-)

By comparing with another project I see that the request to [https://inmuebles.auth0.com/user/ssodata/](https://inmuebles.auth0.com/user/ssodata/) returns 404 and my working project works fine

Am I missing something in my application/tenant configuration??

---

<div class="post-metadata">

**Author:** ![luisguerra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/luisguerra/32/4981_2.png) [@luisguerra](https://community.auth0.com/u/luisguerra)\
**Post date:** [October 29, 2018, 3:03pm UTC](https://community.auth0.com/t/get-last-login-not-working/17084/2 "2018-10-29T15:03:24Z")

</div>

Update: Apparently this is a known issue for the Auth0 team

I reported it under the lock repo and the are working on a solution

> <https://github.com/auth0/lock/issues/1525>
>
> \### Description
> 
> The use case I'm trying to acomplish is login with a user acc…ount in my tenant, logout and when re-enter the login the \`Last time you logged in with\` screen should be displayed
> 
> \### Prerequisites
> 
> \* \[x\] I have read the \[Auth0 general contribution guidelines\](https://github.com/auth0/open-source-template/blob/master/GENERAL-CONTRIBUTING.md)
> \* \[x\] I have read the \[Auth0 Code of Conduct\](https://github.com/auth0/open-source-template/blob/master/CODE-OF-CONDUCT.md)
> \* \[x\] Did you check the documentation in the \[README\](https://github.com/auth0/lock) or on \[our docs site\](https://auth0.com/docs/libraries/lock/v11)?
> \* \[x\] Did you check the \[Auth0 Community\](https://community.auth0.com/)?
> \* \[\] Are you reporting this to the correct repository?
> \* \[\] Are there any related or duplicate \[Issues\](https://github.com/auth0/lock/issues) or \[PRs\](https://github.com/auth0/lock/pulls) for this issue?
> 
> \### Environment
> 
> Please provide the following:
> 
> \* Lock version: 11.11.1
> \* Browser version: Chrome
> \* OS: Windows 10
> 
> \### Reproduction
> 
> Go to \[my login page\](https://inmuebles.auth0.com/login?state=a9Sm\_cORvkd2Nfs-\_SvC1vzIKVmSPfTN&client=ZIt2\_7alkaiuy-bifxBKrcPiy06IerwV&protocol=oauth2&response\_type=token%20id\_token&response\_mode=fragment&redirect\_uri=http%3A%2F%2Flocalhost%3A4200%2Fcallback&scope=openid%20profile%20email&audience=https%3A%2F%2Finmuebles.auth0.com%2Fuserinfo&nonce=bm4jCCJ9HwrkFOMlJejIRXiLMynguxXB&auth0Client=eyJuYW1lIjoiYXV0aDAuanMiLCJ2ZXJzaW9uIjoiOS44LjAifQ%3D%3D) open DevTools and see that the \`/user/ssodata\` endpoint is returnind 404 which holds the information about the last user entered

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [October 29, 2018, 4:08pm UTC](https://community.auth0.com/t/get-last-login-not-working/17084/3 "2018-10-29T16:08:16Z")

</div>

Hey @luisguerra!

Thanks for getting it to wider audience. As said in the issue, this happens because new tenants have our new SSO flow, which doesn’t even show the login page if doesn’t need to. So we decided to remove the /ssodata endpoint for new tenants, since it’s not needed anymore. The problem is that for unauthenticated users, lock will still call the /ssodata endpoint.

We’re working on a solution.

**In the meantime, you can disable the `rememberLastLogin` so lock doesn’t call /ssodata when it loads.**

---

<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:** [November 28, 2018, 4:08pm UTC](https://community.auth0.com/t/get-last-login-not-working/17084/4 "2018-11-28T16:08:18Z")

</div>

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