This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
build20a: Execution calendar samples with Liberty SAML Token profile on a remote AM failed with exception in output server log file: StandardWrapperValve[CalendarServlet]: Servlet.service() for servlet CalendarServlet threw exception java.io.IOException: response handler error: ; nested exception is: javax.xml.rpc.JAXRPCException: com.sun.enterprise.security.jauth.AuthException: Response Validation Failed at com.sun.identity.wss.samples.calendarclient.CalendarServlet.processRequest(CalendarServlet.java:42) at com.sun.identity.wss.samples.calendarclient.CalendarServlet.doGet(CalendarServlet.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Created attachment 34352 [details] appserver log file
Does the other liberty sec mech work on this AM server?
The AS where the calendar samples deployed doesnt talk to the AM server where he configuration is deployed. The calendar projects need to be pointed to the proper Application Server which is configured to talk to the remote AM server. Please try with the proper AS instance and report if this succeeds.
If deploy the application to the same remote appserver and am server, then the application execution is fine.
The matching of App server and the AM server that it can talk to has to be done correctly by the user. This is by design. I recommend we write an article to talk about this relationship in detail. We have it mentioned in the online doc but not in that detail.