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.

Bug 85500 - Execution calendar samples with liberty-SAML token on remote AM failed.
Summary: Execution calendar samples with liberty-SAML token on remote AM failed.
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Identity (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Srividhya Narayanan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-22 00:26 UTC by _ hlu
Modified: 2006-10-07 01:59 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
appserver log file (929.29 KB, text/plain)
2006-09-22 00:28 UTC, _ hlu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ hlu 2006-09-22 00:26:42 UTC
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)
Comment 1 _ hlu 2006-09-22 00:28:27 UTC
Created attachment 34352 [details]
appserver log file
Comment 2 Srividhya Narayanan 2006-09-22 01:19:50 UTC
Does the other liberty sec mech work on this AM server?
Comment 3 Srividhya Narayanan 2006-09-22 19:31:15 UTC
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.
Comment 4 _ hlu 2006-09-22 22:26:59 UTC
If deploy the application to the same remote appserver and am server, then the
application execution is fine.
Comment 5 Srividhya Narayanan 2006-09-22 23:01:50 UTC
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.