# Qutestion: ignore-session-expire VS long session

**URL:** <https://support.openanalytics.eu/t/qutestion-ignore-session-expire-vs-long-session/2684>\
**Category:** ShinyProxy\
**Created:** [December 8, 2023, 1:15pm UTC](https://support.openanalytics.eu/t/qutestion-ignore-session-expire-vs-long-session/2684 "2023-12-08T13:15:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tianjiaolaozu](https://support.openanalytics.eu/user_avatar/support.openanalytics.eu/tianjiaolaozu/32/918_2.png) [@tianjiaolaozu](https://support.openanalytics.eu/u/tianjiaolaozu)\
**Post date:** [December 8, 2023, 1:15pm UTC](https://support.openanalytics.eu/t/qutestion-ignore-session-expire-vs-long-session/2684/1 "2023-12-08T13:15:33Z")

</div>

Hi everyone,  
We are using v3.0.2 and openid for authentication. In the release note of v3.0.2 , It states there is an option “ignore-session-expire” that add the feature to ignore OIDC session expiration. [https://shinyproxy.io/documentation/configuration/#ignore-session-expire](https://shinyproxy.io/documentation/configuration/#ignore-session-expire) but also at the bottom of the same page, it requests to set “servlet.session.timeout” to some value like 3600 to overwrite the default “30mins” since “By default, a session of the HTTP engine embedded in ShinyProxy will time out after 30 minutes”.

Anyone can advise the difference between the 2 parameters? I am wondering whether I need to set both of the two parameters if I want to get a long session like 6 hours. And what is “a session of the HTTP engine embedded in ShinyProxy”? Thanks.

---

<div class="post-metadata">

**Author:** ![tianjiaolaozu](https://support.openanalytics.eu/user_avatar/support.openanalytics.eu/tianjiaolaozu/32/918_2.png) [@tianjiaolaozu](https://support.openanalytics.eu/u/tianjiaolaozu)\
**Post date:** [December 10, 2023, 8:39am UTC](https://support.openanalytics.eu/t/qutestion-ignore-session-expire-vs-long-session/2684/2 "2023-12-10T08:39:42Z")

</div>

and there is an option called “heartbeat-timeout”. I do not quite understand why I may still need to set the “servlet.session.timeout” parameter even thought I have set the “heartbeat-timeout” parameter to a large number.