[MGNLSTK-735] Logout results in session expired error, unable to login again Created: 01/Dec/10 Updated: 19/Jan/11 Resolved: 12/Jan/11 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | 1.4 |
| Fix Version/s: | 1.4.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Antti Hietala | Assignee: | Tobias Mattsson |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Form 1.2.0, PUR 1.3.0 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
A registered public user gets "Session expired" error when they log out. Trying to log back in results in the same error. Expected behavior is clean a logout and a Thank You message. Do this on demoauthor.magnolia-cms.com:
Do this on demopublic.magnolia-cms.com:
|
| Comments |
| Comment by Tobias Mattsson [ 06/Dec/10 ] |
|
While logging in and out works this is performed in filters, that establish or closes the session. Since form 1.2 we keep state in the session so when the filters execute the rest of the form processing fails with the "session expired" error. A solution is to perform login and logout in form processors instead. After these are executed the form must return a redirect to a success page. |
| Comment by Magnolia International [ 21/Dec/10 ] |
|
Just for the record, there's no need to create a public user to reproduce this issue, simply try with superuser/superuser, and observe the same issue. |
| Comment by Tobias Mattsson [ 12/Jan/11 ] |
|
Fixed as of |