Details
-
Improvement
-
Resolution: Obsolete
-
Major
-
None
-
3.1 M3
-
None
Description
For some obscure reason(s), the current LoginFilter calls resetSessionAttributes(HttpSession) when one LoginHandler has succeded (LoginHandler.STATUS_SUCCEDED). It seems to be a workaround, and currently refers to MAGNOLIA-1598 and MAGNOLIA-1605.
I'm trying to implement CAS on Magnolia, and as the CASFilter (which is called by a custom LoginHandler) sets some parameters in session to remember the current user has logged in, it is destroyed by this reset function.
So I'm just asking if it is possible to make that function protected, in order to use my own instance of LoginFilter which would take care of the CASFilter parameters also...
Thanks !
Checklists
Acceptance criteria