How are you configuring WSS4J? Colm.
On Thu, Nov 19, 2015 at 2:13 AM, dthomas <[email protected]> wrote: > What I have now is this: > > <soap:Envelope > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Header> > <ns3:Security xmlns="http://docs.oasis-open.org/ws-sx/ws-trust/200512"; > xmlns:ns2=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd > " > xmlns:ns3=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd > " > xmlns:ns4="http://www.w3.org/2005/08/addressing"; > xmlns:ns5="http://www.rsa.com/names/2009/12/std-ext/WS-Trust1.4/advice"; > xmlns:ns6="urn:oasis:names:tc:SAML:2.0:assertion" > xmlns:ns7="http://www.w3.org/2000/09/xmldsig#"; > xmlns:ns8="http://www.rsa.com/names/2009/12/std-ext/SAML2.0"; > xmlns:ns9="urn:oasis:names:tc:SAML:2.0:conditions:delegation" > soap:mustUnderstand="1"> > > <wsu:Timestamp > xmlns:wsu=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd > " > > wsu:Id="Timestamp-1"><wsu:Created>2015-11-18T16:32:21.705Z</wsu:Created><wsu:Expires>2015-11-18T16:37:21.705Z</wsu:Expires></wsu:Timestamp> > > <ns2:Timestamp xmlns="http://docs.oasis-open.org/ws-sx/ws-trust/200512"; > xmlns:ns2=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd > " > xmlns:ns3=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd > " > xmlns:ns4="http://www.w3.org/2005/08/addressing"; > xmlns:ns5="http://www.rsa.com/names/2009/12/std-ext/WS-Trust1.4/advice"; > xmlns:ns6="urn:oasis:names:tc:SAML:2.0:assertion" > xmlns:ns7="http://www.w3.org/2000/09/xmldsig#"; > xmlns:ns8="http://www.rsa.com/names/2009/12/std-ext/SAML2.0"; > xmlns:ns9="urn:oasis:names:tc:SAML:2.0:conditions:delegation" > > ns2:Id="_32c97089-04ac-49b0-8758-3d176d110ec7"><ns2:Created>2015-11-18T16:32:19.373Z</ns2:Created><ns2:Expires>2015-11-18T16:42:19.373Z</ns2:Expires></ns2:Timestamp> > > ..........Truncated > The < wsu:Timestamp > element is being added by wss4j. The < ns2:Timestamp > > > element is added by a custom timestamp handler. > > How do I prevent wss4j from adding the timestamp element so that there is > only 1 timestamp(the one added by the custom timestamp handler) in the SOAP > header? > > Any help would be appreciated! > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/How-do-I-make-wss4j-not-create-Timestamp-element-in-soap-header-tp5763076.html > Sent from the cxf-dev mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
