Description of problem:

PicketLink AbstractIDPValve does not trigger the next valve in the pipeline.  The invoke() method of the AbstractIDPValve does not called getNext().invoke() which means that the pipeline processing will always terminate with the IDP valve.

You can see this by placing the AccessLogValve after the IDP valve in the WEB-INF/jboss-web.xml file.  The AccessLogValve will not get triggered.


Version-Release number of selected component (if applicable):


Steps to Reproduce:

Stack the ExtendedFormAuthenticator, IDPWebBrowserSSOValve and RequestDumperValve together.  The RequestDumperValve will not get called.

<jboss-web>
    <security-domain>SPNEGO</security-domain>
    <disable-audit>false</disable-audit>
    <context-root>idp</context-root>
    <valve>
      <class-name>org.jboss.as.web.security.ExtendedFormAuthenticator</class-name>
    </valve>
    <valve>
        <class-name>org.picketlink.identity.federation.bindings.tomcat.idp.IDPWebBrowserSSOValve</class-name>
        <param>
            <param-name>passUserPrincipalToAttributeManager</param-name>
            <param-value>true</param-value>
        </param>
        <param>
            <param-name>characterEncoding</param-name>
            <param-value>UTF-8</param-value>
        </param>
   </valve>
    <valve>
      <class-name>org.apache.catalina.valves.RequestDumperValve</class-name>
    </valve>
</jboss-web>


Actual results:
The RequestDumperValve does not get called.


Expected results:
The RequestDumperValve should get called.


Additional info: