[MAGNOLIA-1775] WebContextImpl.logout() should not only logout the jcr sessions but also remove them from the request Created: 11/Oct/07  Updated: 23/Jan/13  Resolved: 11/Oct/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.5 RC1
Fix Version/s: 3.5 RC1

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-1774 LogoutFilter should not set the conte... Closed
relation
is related to MAGNOLIA-1758 WebcontextImpl stores a non-serializa... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

(amongst other things because these will otherwise be retrieved and attempted to be reused, even though they're not live anymore)

A simple way of doing this would be to have the logout method call the release() method; this shows some overlap and again calls for a larger review of the login/logout/context concepts.



 Comments   
Comment by Magnolia International [ 11/Oct/07 ]

does this by simply delegating to the release() method. this means that it only attempts to close sessions which were stored as request attributes, which is a slight change in behaviour, as it was previously attempting to close sessions for all registered workspaces

Generated at Mon Feb 12 03:30:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.