// Update SESSION_LAST_FE_COOKIE if cookie has changed.
if(self::$flagFeUserChanged){
self::set(SESSION_LAST_FE_COOKIE,$cookieFeUser);
}
}else{
}else{
// If we are called through API there is no T3 environment. Assume nothing has changed, and fake the following check to always 'no change'.
// If we are called through API there is no T3 environment. Assume nothing has changed, and fake the following check to always 'no change'.
$feUidLoggedIn=$feUserUidSession;
$feUidLoggedIn=$feUserUidSession;
}
}
if($feUidLoggedIn!=$feUserUidSession){
if($feUidLoggedIn!=$feUserUidSession){
// destroy existing session store
// Session::clearAll(); // #5668 / Broken SIP after login - is it really a security improvement to destroy the SIP store in case the feUser changes? Probably not.
// save new feUserUid, feUserName
// save new feUserUid, feUserName
Session::set(SESSION_FE_USER_UID,$feUidLoggedIn);
Session::set(SESSION_FE_USER_UID,$feUidLoggedIn);
Session::set(SESSION_FE_USER,$feUserSession);
Session::set(SESSION_FE_USER,$feUserSession);
Session::set(SESSION_FE_USER_GROUP,$feUserGroup);
Session::set(SESSION_FE_USER_GROUP,$feUserGroup);
Session::set(SESSION_BE_USER,$beUser);
Session::set(SESSION_BE_USER,$beUser);
// throw new UserFormException("FYI: Session has been cleared. Reload this page. ".
# cat=security/security; type=string; label='GET'-Parameter max length:Default is '50'. GET vars longer than 'x' character triggers an `attack-detected`.
# cat=security/security; type=string; label='GET'-Parameter max length:Default is '50'. GET vars longer than 'x' character triggers an `attack-detected`.
securityGetMaxLength = 50
securityGetMaxLength = 50
# cat=security/security; type=string; label=Session Timeout in seconds:Default is '1800'. After inactivity of 'x' seconds, the user has to relogin.
# cat=security/security; type=string; label=Session Timeout in seconds:Default is empty to take the php.ini system value (minimum of 'session.cookie_lifetime' and 'session.gc_maxlifetime').