Bug #17666

be sessions time out before $TYPO3_CONF_VARS["BE"]["sessionTimeout"]

Added by Hartmut Plehn over 14 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2007-10-10
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.1
PHP Version:
5.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

We notice BE session timeouts. The timeouts occur after some time of inactivity (1-2 hours), that is shorter than the time defined in $TYPO3_CONF_VARS["BE"]["sessionTimeout"]

Some debugging showed that t3lib_userAuth::gc() is called with different values of gc_time. gc_time (and auth_timeout_field) sometimes have the value $TYPO3_CONF_VARS["BE"]["sessionTimeout"] and sometimes are 6000.

Probably there are t3lib_beUserAuth-Objects initialized (by extensions or cli-programs) that do not explicitly set auth_timeout as in init.php. We are using simulatebe, which I suspect being the problem.

Changing auth_timeout_field from 6000 to the value of $TYPO3_CONF_VARS["BE"]["sessionTimeout"] in t3lib/class.t3lib_beuserauth.php seems to fix the problem.

(issue imported from #M6493)


Related issues

Related to TYPO3 Core - Bug #14836: Session-Lifetime for BE-User and FE-User doesnt work in FEClosedChristian Kuhn2005-06-22

Actions
Related to TYPO3 Core - Bug #19153: Insonsistent description/initialisation of class.t3lib_beuserauth.php->auth_timeout_fieldClosed2008-07-25

Actions
Related to TYPO3 Core - Bug #21511: Lots of HTML, JS and/or CSS errors force IE8 to switch to compatibility viewClosed2009-11-09

Actions
Related to TYPO3 Core - Bug #17808: Ajax relogin won't relogin and ignores [BE][sessionTimeout]ClosedSteffen Gebert2010-06-01

Actions

Also available in: Atom PDF