Removing timestamp in WSE 2.0

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jan - 24 Apr 2006 06:40 GMT

I am developing WSE 2.0 .NET client consuming Java Web services and I need to
remove timestamp from outgoing SOAP message.

I implemented the SoapOutputFilter but it seems that in ProcessMessage
method Security element doesn't exist YET and therefore I cannot remove
timestamp.
I can see other header elements like Action, MessageID, ReplyTo and To but
there is no Security element and therefore no timestamp.

Here is code example:

XmlNamespaceManager nsm = new XmlNamespaceManager(envelope.NameTable );
nsm.AddNamespace("wsse", WSSecurity.NamespaceURI);
nsm.AddNamespace("wsu", WSUtility.NamespaceURI);
XmlNode node =
envelope.Header.SelectSingleNode("//wsse:Security/wsu:Timestamp", nsm);

I need to remove Timestamp completely since the configuration of the Java
web service I am calling doesn't support it. If I add timestamp to Java web
service configuration it works just fine but I cannot do it since it would
not be compatible with other existing java clients.

Any help is highly appreciated

Jan

Reply to this Message

Pablo Cibraro - 24 Apr 2006 15:05 GMT

Hi Jan,

Did you configure your assertion to run after the security assertion ?. The
order of the assertions is really important.

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax

>I am developing WSE 2.0 .NET client consuming Java Web services and I need
>to
[quoted text clipped - 23 lines]
>
> Jan

Reply to this Message

Jan - 24 Apr 2006 15:21 GMT

Hi Pablo,
thank you for your response. I am not quite sure what you mean. This is
from WSE 2.0 documentation:

The order in which filters are processed is as follows:
1. Security
2. Timestamp
3. Referral
4. Routing
5. Custom filters

I implemented custom filter (:SoapOutputFilter) and also security filter (:
SecurityOutputFilter) but both of them failed. By that I mean that security
header was not created in runtime yet.

Can you be please more specific and give me some example how to do this?

Thank you.

Jan

> Hi Jan,
>
[quoted text clipped - 32 lines]
> >
> > Jan

Reply to this Message

Pablo Cibraro - 24 Apr 2006 21:43 GMT

Upss, sorry. I was talking about WSE 3.0.
I am not sure how to do the same with WSE 2.0.

Regards,
Pablo.

> Hi Pablo,
> thank you for your response. I am not quite sure what you mean. This is
[quoted text clipped - 60 lines]
>> >
>> > Jan

Reply to this Message

Jan - 25 Apr 2006 06:02 GMT

Can you discribe how do you do it with WSE 3.0 please?

Jan

> Upss, sorry. I was talking about WSE 3.0.
> I am not sure how to do the same with WSE 2.0.
[quoted text clipped - 66 lines]
> >> >
> >> > Jan

Reply to this Message

Pablo Cibraro - 25 Apr 2006 15:35 GMT

Yes,

You have to perform the following steps:

1. Develop a custom assertion (An assertion is a kind of factory for the
soap filters)
2. Develop an output filter to remove the timestamp header

3. Configure the service to use a policy with two assertions, the security
assertion and the assertion developed in the step #1. (The last one must run
after the security assertion).

You can find more information about this topic in this article
http://msdn.microsoft.com/msdnmag/issues/06/02/WSE30/default.aspx

Regards,
Pablo.

> Can you discribe how do you do it with WSE 3.0 please?
>
[quoted text clipped - 80 lines]
>> >> >
>> >> > Jan

Reply to this Message

Jan - 26 Apr 2006 06:18 GMT

Pablo,
this is excellent! This should work. I will implement my client with WSE
3.0 and try what you suggested. I will update you once I am done.

Thank you very much for your resposne.

All the best!

Jan

> Yes,
>
[quoted text clipped - 98 lines]
> >> >> >
> >> >> > Jan

Reply to this Message

Removing timestamp in WSE 2.0

Free Magazines