Hi Adrian,
On Wed, Sep 01, 2004 at 12:24:14PM +0800, Adrian Chadd wrote:
> 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.
Sure! A session idle timeout is really useful. :)
The patch is fine! :)
Anyway. OTRS 1.3 comes also with an idle timeout config option. The
default is 4 hours.
[Kernel/Config.pm]
# SessionMaxIdleTime
# (After this time (in seconds) without new http request, then
# the user get logged off)
$Self->{SessionMaxIdleTime} = 4*60*60;
[...]
Thanks for your help! :)
> Adrian
>
> --
> Adrian Chadd The University of Western Australia
Martin Edenhofer
--
((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg
http://www.otrs.de/ :: Manage your communication!
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
