Bug #24873
closedOpen forms cannot be saved after "Relogin" (Security Token errors)
0%
Description
If you have an open form (e.g. editing a content element) and you leave your browser unattended until "session expires", you can relogin with the popup window (or the JS overlay).
After this relogin, if you try to save your work, you will get security token errors.
The CSRF protection token is in a hidden field, and if the session has expired in the meantime, the session data (including the original tokens) are gone, so when saving that form after the relogin won't be able to validate them. Different potential solutions:
a) go through the DOM and manipulate all hidden fields with a token and change them with a new valid token. doable, but will require some work
b) allow "one save without token check" right after the relogin, so that this form can be finally saved, and after that things continue as usual.
(issue imported from #M17383)
Files
Updated by Ernesto Baschny almost 14 years ago
Hi Helmut, you wanted to take a look at it. :) Thanks!
Updated by Peter Niederlag almost 14 years ago
I am 99% percent sure the issue (#24755) shows up as well without any open form/data:
login.... wait ... expire ... relogin -> error messages
Updated by Ernesto Baschny almost 14 years ago
Yes, peter, but these are most probably the ExtDirect errors, see #24870.
If there is yet another category of errors, please open another issue for this ;)
Thanks!
Updated by Steffen Kamper over 13 years ago
Committed to svn
4_5 rev 10519
trunk rev 10520