Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
None
-
None
Description
This causes an error for users using the UI if users are idle in their browser for 30 minutes, then go to use the Grouper UI. I would think this should be set to the same as max session length of the enclosing authentication.
We can have an env variable that would allow this to be set, and have a better default (10 hours for UI, 1 min for WS which doesnt have sessions anyways?)
GROUPER_TOMCAT_SESSION_TIMEOUT_MINUTES = 600
Something like this
#Replace web.xml session timeout with env variable
|
if [[ -z "${GROUPER_TOMCAT_SESSION_TIMEOUT_MINUTES}" ]]; then |
echo "grouperContainer; INFO: (...) $ GROUPER_TOMCAT_SESSION_TIMEOUT_MINUTES is not set, setting to default of 600 (10 hours)" |
fi
|
# dont blank this out if the var isnt there |
sed -i "s|<session-timeout>30</session-timeout>|<session-timeout>$GROUPER_TOMCAT_SESSION_TIMEOUT_MINUTES</session-timeout>|g" /opt/tomee/conf/web.xml |
echo "grouperContainer; INFO: (grouperScriptHooks.sh-grouperScriptHooks_setupFilesPost) based on GROUPER_TOMCAT_SESSION_TIMEOUT_MINUTES, sed -i ''s|<session-timeout>30</session-timeout>|<session-timeout>$GROUPER_TOMCAT_SESSION_TIMEOUT_MINUTES</session-timeout>|g'' /opt/tomee/conf/web.xml , result=$?" |
|