Hi all,
I've hit a bit of a snag with session timeouts in OTRS. Specifically,
the hard session timeout value is a bit inflexible - people will leave
their browsers on overnight and continue using OTRS when they arrive
in the office in the morning.
A timeout of 24 hours let this work, but only up until 24 hours.
The session would then go dead right on time - in the middle of their
work.
I've written a patch to store a new key in the session information,
UserSessionLastTime. It is updated with time() whenever the session
information is read or updated. I then use this to check whether
the session is invalid. The session now lasts MaxSessionTime minutes of
idle time instead of the session lasting 24 hours after login.
I've attached the patch below. I'm not sure whether people will find
this behaviour more useful than the current behaviour.
Thanks!
Adrian
--
Adrian Chadd The University of Western Australia