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.
The RequestDumperValve does not get called.
The RequestDumperValve should get called.
Pedro Igor <firstname.lastname@example.org> updated the status of jira PLINK-516 to Resolved
This fix needs to include PLINK-516 and PLINK-546.
The fix in PLINK-516 does not completely resolve the issue. With only the PLINK-516 fix, the ClusteredSessionValve does not get invoked. This breaks the clustered session replication functionality.
Pedro Igor <email@example.com> updated the status of jira PLINK-546 to Resolved
Fix for PLINK-516 does not work for me. For JBoss EAP 6.3.2.CR1, with RequestDumperValve and ExtendedFormAuthenticator added, requests are dumped to log twice.
Commits in PicketLink 2.5.3.SP11-redhat-1 are in wrong order. PLINK-558 commit is the important one and should be placed as the last one. See BZ 1122717.
To be precise: commits in PicketLink Bindings 2.5.3.SP11-redhat-1.
Fixed in 2.5.3.SP12.
Verified for EAP 6.3.2.CR2