This discussion is archived
8 Replies Latest reply: Sep 21, 2012 4:32 AM by user696 RSS

Weblogic 10.3 - SOAP Respose - Timestamp not in UTC Format

910015 Newbie
Currently Being Moderated
While hitting a webservice through weblogic, I am getting the response Soap Header->Security->Timestamp->Created & Expires which are not in UTC format. I can see additional check have been added to weblogic.xml.crypto.wss.TimestampImpl to make sure that these time are there in the UTC format.

Is there any way I can skip the same and accept the time without being in the UTC format?



Error Trace:


[WssHandler] : class weblogic.wsee.security.wssp.handlers.PreWssClientPolicyHandler.handleRequest
** Request: weblogic.xml.saaj.SOAPMessageImpl@1d592a
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><m:Login xmlns:m="http://www.xxx.com/abc/Test"><m:Username>testUser</m:Username><m:Password>testPassword</m:Password></m:Login></env:Body></env:Envelope>
[WssHandler] : class weblogic.wsee.security.wssp.handlers.WssClientHandler.handleRequest
[WssHandler] : class weblogic.wsee.security.wssp.handlers.PostWssClientPolicyHandler.handleRequest
[WssHandler] : class weblogic.wsee.security.wssp.handlers.PostWssClientPolicyHandler.handleResponse
[WssHandler] : class weblogic.wsee.security.wssp.handlers.WssClientHandler.handleResponse
java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}InvalidSecurity] FaultString [weblogic.xml.dom.marshal.MarshalException: xsd:dateTime element does not have required UTC time zone.] FaultActor [null]No Detail; nested exception is:
weblogic.wsee.jaxrpc.soapfault.WLSOAPFaultException: weblogic.xml.dom.marshal.MarshalException: xsd:dateTime element does not have required UTC time zone.
at com.kbb3.webservice.IVehicleInformationService2008R2_Stub.login(Unknown Source)
at TestMain.main(TestMain.java:30)
Caused by: weblogic.wsee.jaxrpc.soapfault.WLSOAPFaultException: weblogic.xml.dom.marshal.MarshalException: xsd:dateTime element does not have required UTC time zone.
at weblogic.wsee.codec.soap11.SoapCodec.decodeFault(SoapCodec.java:355)
at weblogic.wsee.ws.dispatch.client.CodecHandler.decodeFault(CodecHandler.java:115)
at weblogic.wsee.ws.dispatch.client.CodecHandler.decode(CodecHandler.java:100)
at weblogic.wsee.ws.dispatch.client.CodecHandler.handleFault(CodecHandler.java:88)
at weblogic.wsee.handler.HandlerIterator.handleFault(HandlerIterator.java:309)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:269)
at weblogic.wsee.ws.dispatch.client.ClientDispatcher.handleResponse(ClientDispatcher.java:213)
at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:150)
at weblogic.wsee.ws.WsStub.invoke(WsStub.java:87)
at weblogic.wsee.jaxrpc.StubImpl._invoke(StubImpl.java:337)
... 2 more
Caused by: weblogic.xml.crypto.wss.WSSecurityException: weblogic.xml.dom.marshal.MarshalException: xsd:dateTime element does not have required UTC time zone.
at weblogic.wsee.security.wssp.handlers.WssClientHandler.processInbound(WssClientHandler.java:146)
at weblogic.wsee.security.wssp.handlers.WssClientHandler.processResponse(WssClientHandler.java:132)
at weblogic.wsee.security.wssp.handlers.WssHandler.handleResponse(WssHandler.java:133)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:287)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:271)
... 6 more
Caused by: weblogic.xml.dom.marshal.MarshalException: xsd:dateTime element does not have required UTC time zone.
at weblogic.xml.crypto.wss.TimestampImpl.ensureUTC(TimestampImpl.java:160)
at weblogic.xml.crypto.wss.TimestampImpl.unmarshalCreated(TimestampImpl.java:138)
at weblogic.xml.crypto.wss.TimestampImpl.unmarshal(TimestampImpl.java:108)
at weblogic.xml.crypto.wss.SecurityImpl.unmarshalAndProcessTimestamp(SecurityImpl.java:605)
at weblogic.xml.crypto.wss.SecurityImpl.unmarshalChildren(SecurityImpl.java:505)
at weblogic.xml.crypto.wss.SecurityImpl.unmarshalInternal(SecurityImpl.java:448)
at weblogic.xml.crypto.wss.SecurityImpl.unmarshal(SecurityImpl.java:416)
at weblogic.xml.crypto.wss11.internal.WSS11Factory.unmarshalAndProcessSecurity(WSS11Factory.java:33)
at weblogic.wsee.security.wssp.handlers.WssClientHandler.processInbound(WssClientHandler.java:143)
... 10 more


When I hit the same service through SOAPUI, I am able to get the response without any issues.

The response received using SOAPUI can be seen at: http://postimage.org/image/ifkfaa9j5/

I haven't applied any policy at my end.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points