Bug #37001

Catch Exception from inactivityTimeout

Added by Carsten Bleicker over 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Must have
Category:
Security
Target version:
-
Start date:
2012-05-09
Due date:
% Done:

100%

Estimated time:
PHP Version:
5.3
Has patch:
No
Complexity:

Description

i played around a little bit with the session lifetime.
setting inactivityTimeout: 30
on inactivity for about 30 seconds flow3 throws the exception:
"#1258721059: The security context contained no tokens which could be authenticated"
Should this be catched and force a redirect to the default configured auth provider?


Related issues

Related to TYPO3.Flow - Feature #39423: Custom Error RenderersResolvedBastian Waidelich2012-12-25

Actions
Related to TYPO3.Flow - Feature #29907: Redirect to /login instead of raising a "Entity not found." exception if the userdata of an active session has been deletedResolvedKarsten Dambekalns2011-09-16

Actions
Has duplicate TYPO3.Flow - Feature #37243: Authentication after long time of inactivityClosedKarsten Dambekalns2012-05-17

Actions
Has duplicate TYPO3.Flow - Bug #40563: When session times out, Exception occurs instead of WebRedirectClosed2012-09-03

Actions

Also available in: Atom PDF