Re: Host "change password"-page on IDP
mksplg Oct 19, 2012 12:17 PMIt works to host a JSF index site if there is a index.jsf and index.xhtml present.
However it's apparently not possible to link any resources (images/css) in the page. For example when adding an image with <h:graphicImage library="gfx" name="test.png"/> the image is shown but this exception is thrown:
An exception or error occurred in the container during the request processing: java.lang.IllegalStateException: Cannot forward after response has been committed at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:417) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407) [jbossweb-7.0.10.Final.jar:] at org.picketlink.identity.federation.bindings.tomcat.idp.AbstractIDPValve.invoke(AbstractIDPValve.java:399) [picketlink-jbas7-2.1.5.Final.jar:2.1.5.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
If the image is linked directly with <img src="resources/gfx/test.png"/> the same exception is thrown but nothing is displayed.
Maybe this has something to do with Picketlink intercepting ALL requests (even requests to stuff that has no <auth-constraint/>s defined and trying to load "/hosted/" instead. Is there anything I miss here, or is this expected?