Issue Bug Rejected

#61754Calling FrontendUserAuthentication->storeSessionData twice prevents setting of FE cookie

Daniel Minder 09/20/14, 00:05 updated 09/01/20, 16:19

Description

I’ve encountered this problem when using sr_freecap with pbsurvey after entering the correct captcha.

The session data is cleared with setKey() and then stored with storeSessionData() in sr_freecap. Afterwards, pbsurvey sets new session data. However, when storeSessionData() is called later on, neither the data is stored in fe_session_data nor the cookie fe_typo_user is set.

Thus, either storeSessionData() must not be called manually in user classes (except before calling exit) – however this is not documented – or storeSessionData() needs to be changed in such a way that it is possible to remove all session data first and adding new session data afterwards, including forcing the cookie. I’ve added a patch for this.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.