This article provides step-by-step instructions on how to configure automatic logout for idle sessions in Jetpatch. It covers settings adjustments for both GWT (Google Web Toolkit) pages and Tomcat session-managed pages. By default, Jetpatch sets a 15-minute idle session timeout for GWT pages and a 30-minute timeout for Tomcat sessions.
Configuring Automatic Logout for Idle Sessions
-
Adjusting Idle Session Timeout for GWT Pages
- Locate the intigua.properties File: Access the JetPatch Manager on the application server. Navigate to
/usr/share/tomcat/default/conf/
. - Edit the File: Open the
intigua.properties
file with a text editor. - Set the Timeout: To configure the automatic logout for idle GWT pages, find or add the line
ui.userIdle.timeout.minutes
. The default isui.userIdle.timeout.minutes=15
. Replace15
with your desired timeout duration in minutes to change the idle session timeout. - Example of Default Setting:
ui.userIdle.timeout.minutes=15
- Save Changes and Restart: Save the file and restart the Jetpatch service to apply the new settings.
- Locate the intigua.properties File: Access the JetPatch Manager on the application server. Navigate to
-
Adjusting Idle Session Timeout for Tomcat Sessions
- Access the web.xml File: In the JetPatch application server, locate the Tomcat configuration file at
/usr/share/tomcat/default/conf/web.xml
. - Edit Session Timeout: In the
web.xml
file, find the<session-config>
section. Inside, locate the<session-timeout>
tag. The default value is set for 30 minutes. - Modify the Timeout: Change the value within
<session-timeout>
to your preferred duration in minutes to adjust the idle session timeout. - Example of Default Setting:
<session-timeout>30</session-timeout>
- Save and Restart: After making the changes, save the
web.xml
file and restart the Tomcat service to implement the changes.
- Access the web.xml File: In the JetPatch application server, locate the Tomcat configuration file at
Comments
0 comments
Please sign in to leave a comment.