# SSO Plugin Account login timed out, please try logging in again

**URL:** <https://meta.discourse.org/t/sso-plugin-account-login-timed-out-please-try-logging-in-again/37341>\
**Category:** Product Support\
**Created:** [31 בדצמבר,‏ 2015,‏ 8:17pm UTC](https://meta.discourse.org/t/sso-plugin-account-login-timed-out-please-try-logging-in-again/37341 "2015-12-31T20:17:05Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![depeters](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/depeters/32/137579_2.png) [@depeters](https://meta.discourse.org/u/depeters)\
**Post date:** [31 בדצמבר,‏ 2015,‏ 8:17pm UTC](https://meta.discourse.org/t/sso-plugin-account-login-timed-out-please-try-logging-in-again/37341/1 "2015-12-31T20:17:05Z")

</div>

I have a link that goes directly to [http://discourse.abecorn.com/users/{username}/messages](http://discourse.abecorn.com/users/%7Busername%7D/messages).

If it has been a while since visiting that link the user will get “Account login timed out, please try logging in again.” If I visit the exact link again, the user is successfully logged in and I do not receive the error message. My question is: if the account login is timed out, why doesn’t the discourse system go ahead and call my external sso url like it does the second time? It’s as if, first, the user has to attempt going to a url in discourse and get the error message. Discourse notices and saves some setting. The second time, discourse knows the user is logged out and correctly calls the sso flow. Why can’t it immediately call the sso flow and skip the “Account login timed out” error? In fact, it seems in previous versions of Discourse I did not have this problem.

---

_[View the full topic](https://meta.discourse.org/t/sso-plugin-account-login-timed-out-please-try-logging-in-again/37341)._
