Bug #61754
closedCalling FrontendUserAuthentication->storeSessionData twice prevents setting of FE cookie
0%
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.
Files
Updated by Benni Mack over 4 years ago
- Status changed from New to Needs Feedback
Do you have this issue with v9? Is this related to a logged-in user or a anonymous user session?
Updated by Benni Mack about 4 years ago
- Status changed from Needs Feedback to Rejected
Closing this issue as there was no feedback. If you still encounter this issue, let me know so I will re-open the ticket.