[
http://jira.magnolia.info/browse/MAGNOLIA-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Joseph updated MAGNOLIA-1726:
-------------------------------------
Fix Version/s: 3.6
> Trying to don't remove some important session attributes when loging in
> -----------------------------------------------------------------------
>
> Key: MAGNOLIA-1726
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1726
> Project: Magnolia
> Issue Type: Improvement
> Components: security
> Affects Versions: 3.1 M3
> Reporter: Anthony Ogier
> Assignee: Sameer Charles
> Fix For: 3.6
>
> Attachments: LoginFilter.java.diff
>
> Original Estimate: 1 minute
> Remaining Estimate: 1 minute
>
> 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 !
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
