We have received questions about stretching the Session Timeout. I'd like to share following post: https://www.linkedin.com/pulse/why-your-app-needs-short-session-timeout-google-facebook-geoff-wilson/ on LinkedIn, which provides some thoughts on why it is not smart to allow a long period where users are not actually using your application but still keep it going.

WEM currently has an extended Session Timeout (135 minutes) in the Runtime, which is already longer than best practices tend to dictate. 

You should in any case use a specific Flowchart you can set as Custom Error Handler (in Portal Settings) for the Session Expired situation, so when this happens you can provide your users with a message and guide them to the starting point of your portal, or to a specific Login flow if you have one, to start a new session. Our Basic Authentication v2020 Example Project (available in the WEM App Store) provides a basic example of this feature.

Changes to settings for Session Timout on current Shared Cloud are not possible. In future, this will be possible if projects are migrated to WEM Kubernetes Runtime cloud (currently only available as private cloud, towards end of 2024 new shared cloud options may be available). 

Ralph - WEM Xpert since 2011