[jboss-jira] [JBoss JIRA] Resolved: (JBAS-6212) PrincipalSessionAttributeFilter does not forward request to next filter/resource in chain.

[Andrew Oliver (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Oliver resolved JBAS-6212.
---------------------------------

    Resolution: Duplicate Issue


https://jira.jboss.org/jira/browse/JBAS-6616 - although this was first, the other one got the work done to it.

> PrincipalSessionAttributeFilter  does not forward request to next filter/resource in chain.
> -------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6212
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6212
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.3.GA
>         Environment: Windows, JBoss 4.2.3, Spring MVC
>            Reporter: Micah Cleveland
>
> I noticed that when the PrincipalSessionAttributeFilter is enabled within JBOSS and you try to navigate in a browser to a web app resource, the resource never gets call because the filter does not foward to the next filter/resource in the chain.
> I was hoping by enabling this filter I would have a way to call my custom login modules logout operation on session expiration.  At a minimum enable me to get the principal name so that I can make appropriate database logout calls.
> It was my understanding that the PrincipalSessionAttributeFilter would place the Principal within the session so that I could access it within a SessionListener when the session is destroyed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira