You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@cxf.apache.org by cxf newbie <ca...@gmail.com> on 2014/03/10 15:03:01 UTC

Timestamp reference not valid after signing message

Hi,

final Map<String, String> outTransformElements = new TreeMap<String,
String>();
outTransformElements.put("{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp",
"wsu:Timestamp
xmlns:wsu=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd\"");

If I put above code then after signing this portion of soap is generated:

<wsu:Timestamp
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="TS-E21BA5812DCCD6A27C13944595876491"><wsu:Created>2014-03-10T13:53:07.633Z</wsu:Created><wsu:Expires>2014-03-10T13:58:07.633Z</wsu:Expires></wsu:Timestamp
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

How can I remove namespace from end element ?
I am forced to do this because timestamp reference can not be validated on
return to the client side.

But namespace in end tag generates this:
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
character 'x' (code 120) in end tag Expected '>'.

Thanks.



--
View this message in context: http://cxf.547215.n5.nabble.com/Timestamp-reference-not-valid-after-signing-message-tp5741018.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: Timestamp reference not valid after signing message

Posted by cxf newbie <ca...@gmail.com>.

Just a note.

This problem becomes this one:

http://cxf.547215.n5.nabble.com/Timestamp-valid-only-with-double-timestamp-reference-td5741140.html



--
View this message in context: http://cxf.547215.n5.nabble.com/Timestamp-reference-not-valid-after-signing-message-tp5741018p5741448.html
Sent from the cxf-user mailing list archive at Nabble.com.