# Network errors on session timeout when using SSO

**URL:** <https://meta.discourse.org/t/network-errors-on-session-timeout-when-using-sso/105935>\
**Category:** Product Support\
**Created:** [January 7, 2019, 6:33pm UTC](https://meta.discourse.org/t/network-errors-on-session-timeout-when-using-sso/105935 "2019-01-07T18:33:18Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [January 8, 2019, 9:35am UTC](https://meta.discourse.org/t/network-errors-on-session-timeout-when-using-sso/105935/2 "2019-01-08T09:35:10Z")

</div>

> [@crispygoth](#):
>
> One of the requirements of this integration is that we need to implement a short session timeout to match the main site. Currently I have the maximum session length set to Discourse’s minimum of 1 hour. It seems like setting this does work and the session does expire, however, the way this interacts with the SSO feature seems to be a bit broken – if I leave my browser tab idle for over an hour, coming back and clicking on any of the links (such as “Top” or “Latest”) results in a network error:

I believe this is a known issue, perhaps @sam can offer some thoughts.

---

_[View the full topic](https://meta.discourse.org/t/network-errors-on-session-timeout-when-using-sso/105935)._
