Configure Session Timeouts
With Operations Hub, you can configure how soon a login session expires when a session is idle.
Before doing so, consider which application sessions you need to configure. The Designer, the End-app, and Proficy Authentication (formerly UAA) each can have its session timeout configured independently.
Operations Hub Session Timeouts
Access the web.xml
file from these locations, and update the
configuration as follows, for End-app and Designer session timeouts respectively:
C:\Program Files\GE\Operations Hub\iqp-tomcat\webapps\app\WEB-INF
C:\Program Files\GE\Operations Hub\iqp-tomcat\webapps\site\WEB-INF
<session-config>
<session-timeout>30</session-timeout>
</session-config>
web.xml
) is not shorter than the session
timeout as shown
here:<session-config>
<session-timeout>2</session-timeout>
<cookie-config> <max-age>120</max-age> </cookie-config>
</session-config>
session-timeout
and cookie-config/max-age
are in different units of measurement (see
note below).Additionally, if you set either of the session timeouts greater than one hour in
web.xml
, you also need to add a system environment variable
SESSION_DESTROY_TIMEOUT
with value session_timeout_in_millisec + 10
minutes in millisec
. For example, if you set a session timeout to two hours,
then set it to 130 * 60 * 1000 = 7800000
.
- Restart IQP tomcat service whenever you reconfigure any of the settings/parameters mentioned above.
session-timeout
is measured in minutes, whereascookie-config/max-age
is measured in seconds.- Any manual configuration changes, including changes for timeouts, are overwritten on upgrade.
For details on configuring session timeouts in Proficy Authentication, refer to the Session Timeout in Proficy Authentication section in the Configuration Hub Help.