# 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:** 3

<div class="post-metadata">

**Author:** ![crispygoth](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@crispygoth](https://meta.discourse.org/u/crispygoth)\
**Post date:** [February 14, 2019, 10:58am UTC](https://meta.discourse.org/t/network-errors-on-session-timeout-when-using-sso/105935/3 "2019-02-14T10:58:30Z")

</div>

Hi, just wondering if anyone’s had chance to look at this? Is there anything I can do to my config or the way my SSO works to sort out this behaviour? We have full control over the code behind the SSO endpoint, so in theory we can do pretty much anything we need to in response to the SSO requests – e.g. is there a way we can provide the required SSO response and redirect back to the AJAX endpoint from the original request?

---

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