We're trying to get DFS working, but we keep on hitting a brick wall with an authorization failure:
"Authorization failed, could not find identities in service context with token "vbxl103/172.16.0.153-1224502489775-1689081137766683002-205""
We are registering the context using the request as in the attached RegisterContext2.xml.
The token and JSESSIONID are then used to send the request as in SoapQuery.xml.
Even though both the JSESSIONID and the token are properly inserted, DFS doesn't seem to be able to match the two requests and returns
HTTP/1.1 500 Internal Server Error Date: Mon, 20 Oct 2008 11:34:49 GMT Transfer-Encoding: chunked Content-Type: text/xml;charset="utf-8" X-Powered-By: Servlet/2.4 JSP/2.0 <?xml version="1.0"?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope"><faultcode>ns2:Server</faultcode><faultstring>Authorization failed, could not find identities in service context with token "vbxl103/172.16.0.153-1224502489775-1689081137766683002-205"</faultstring><detail><ns8:SerializableException xmlns:ns8="http://rt.fs.documentum.emc.com/" xmlns:ns2="http://query.core.datamodel.fs.documentum.emc.com/" xmlns:ns3="http://properties.core.datamodel.fs.documentum.emc.com/" xmlns:ns4="http://core.datamodel.fs.documentum.emc.com/" xmlns:ns5="http://core.services.fs.documentum.emc.com/" xmlns:ns6="http://profiles.core.datamodel.fs.documentum.emc.com/" xmlns:ns7="http://content.core.datamodel.fs.documentum.emc.com/"><exceptionBean><exceptionClass>com.emc.documentum.fs.rt.AuthenticationException</exceptionClass><genericType>java.lang.Exception</genericType><message>Authorization failed, could not find identities in service context with token "vbxl103/172.16.0.153-1224502489775-1689081137766683002-205"</message><stackTrace><className>com.emc.documentum.fs.rt.impl.handler.AuthorizationHandler</className><fileName>AuthorizationHandler.java</fileName><lineNumber>48</lineNumber><methodName>handleMessage</methodName></stackTrace><stackTrace><className>com.emc.documentum.fs.rt.impl.handler.AuthorizationHandler</className><fileName>AuthorizationHandler.java</fileName><lineNumber>1</lineNumber><methodName>handleMessage</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.handler.HandlerProcessor</className><fileName>HandlerProcessor.java</fileName><lineNumber>284</lineNumber><methodName>callHandleMessage</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.handler.HandlerProcessor</className><fileName>HandlerProcessor.java</fileName><lineNumber>135</lineNumber><methodName>callHandlersRequest</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.handler.ServerSOAPHandlerTube</className><fileName>ServerSOAPHandlerTube.java</fileName><lineNumber>181</lineNumber><methodName>callHandlersOnRequest</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.handler.HandlerTube</className><fileName>HandlerTube.java</fileName><lineNumber>114</lineNumber><methodName>processRequest</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.api.pipe.Fiber</className><fileName>Fiber.java</fileName><lineNumber>595</lineNumber><methodName>__doRun</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.api.pipe.Fiber</className><fileName>Fiber.java</fileName><lineNumber>554</lineNumber><methodName>_doRun</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.api.pipe.Fiber</className><fileName>Fiber.java</fileName><lineNumber>539</lineNumber><methodName>doRun</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.api.pipe.Fiber</className><fileName>Fiber.java</fileName><lineNumber>436</lineNumber><methodName>runSync</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.server.WSEndpointImpl$2</className><fileName>WSEndpointImpl.java</fileName><lineNumber>243</lineNumber><methodName>process</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit</className><fileName>HttpAdapter.java</fileName><lineNumber>444</lineNumber><methodName>handle</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.transport.http.HttpAdapter</className><fileName>HttpAdapter.java</fileName><lineNumber>244</lineNumber><methodName>handle</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.transport.http.servlet.ServletAdapter</className><fileName>ServletAdapter.java</fileName><lineNumber>135</lineNumber><methodName>handle</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.transport.http.servlet.WSServletDelegate</className><fileName>WSServletDelegate.java</fileName><lineNumber>129</lineNumber><methodName>doGet</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.transport.http.servlet.WSServletDelegate</className><fileName>WSServletDelegate.java</fileName><lineNumber>160</lineNumber><methodName>doPost</methodName></stackTrace><stackTrace><className>com.sun.xml.ws.transport.http.servlet.WSServlet</className><fileName>WSServlet.java</fileName><lineNumber>75</lineNumber><methodName>doPost</methodName></stackTrace><stackTrace><className>javax.servlet.http.HttpServlet</className><fileName>HttpServlet.java</fileName><lineNumber>763</lineNumber><methodName>service</methodName></stackTrace><stackTrace><className>javax.servlet.http.HttpServlet</className><fileName>HttpServlet.java</fileName><lineNumber>856</lineNumber><methodName>service</methodName></stackTrace><stackTrace><className>weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction</className><fileName>StubSecurityHelper.java</fileName><lineNumber>225</lineNumber><methodName>run</methodName></stackTrace><stackTrace><className>weblogic.servlet.internal.StubSecurityHelper</className><fileName>StubSecurityHelper.java</fileName><lineNumber>127</lineNumber><methodName>invokeServlet</methodName></stackTrace><stackTrace><className>weblogic.servlet.internal.ServletStubImpl</className><fileName>ServletStubImpl.java</fileName><lineNumber>283</lineNumber><methodName>execute</methodName></stackTrace><stackTrace><className>weblogic.servlet.internal.ServletStubImpl</className><fileName>ServletStubImpl.java</fileName><lineNumber>175</lineNumber><methodName>execute</methodName></stackTrace><stackTrace><className>weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction</className><fileName>WebAppServletContext.java</fileName><lineNumber>3214</lineNumber><methodName>run</methodName></stackTrace><stackTrace><className>weblogic.security.acl.internal.AuthenticatedSubject</className><fileName>AuthenticatedSubject.java</fileName><lineNumber>321</lineNumber><methodName>doAs</methodName></stackTrace><stackTrace><className>weblogic.security.service.SecurityManager</className><fileName>SecurityManager.java</fileName><lineNumber>121</lineNumber><methodName>runAs</methodName></stackTrace><stackTrace><className>weblogic.servlet.internal.WebAppServletContext</className><fileName>WebAppServletContext.java</fileName><lineNumber>1983</lineNumber><methodName>securedExecute</methodName></stackTrace><stackTrace><className>weblogic.servlet.internal.WebAppServletContext</className><fileName>WebAppServletContext.java</fileName><lineNumber>1890</lineNumber><methodName>execute</methodName></stackTrace><stackTrace><className>weblogic.servlet.internal.ServletRequestImpl</className><fileName>ServletRequestImpl.java</fileName><lineNumber>1344</lineNumber><methodName>run</methodName></stackTrace><stackTrace><className>weblogic.work.ExecuteThread</className><fileName>ExecuteThread.java</fileName><lineNumber>209</lineNumber><methodName>execute</methodName></stackTrace><stackTrace><className>weblogic.work.ExecuteThread</className><fileName>ExecuteThread.java</fileName><lineNumber>181</lineNumber><methodName>run</methodName></stackTrace></exceptionBean><message>Authorization failed, could not find identities in service context with token "vbxl103/172.16.0.153-1224502489775-1689081137766683002-205"</message></ns8:SerializableException></detail></ns2:Fault></S:Body></S:Envelope>
(We are running 6SP1)
