Hi Pablo Cibraro,
According to your document, when we apply WS-Security 1.0 in both client and
Server application it will work.
I have created the Client (Windows application) by using Visual studio 2003
and applied the policy by using WSE 2.0 (WS-security 1.0). Moreover I tried
to create a Webservice in Visual studio 2005 and applied the policy
(WS-Security 1.1).
It is not working, hoping we need to apply WS-Security 1.0 in the webservice.
Can u just tell me How should the apply WS-security 1.1 in WSE3.0?
> Hi,
>
[quoted text clipped - 23 lines]
> > Hoping it won't work!! I want to know is there other possibility available
> > (Interoperability) ?
Pablo Cibraro - 30 May 2006 15:14 GMT
Hi,
When you define a policy for WSE 3.0, it uses WS-Security 1.1 or 1.0
depending on the different security features that you want to use.
The configuration tool provided by WSE 3.0 has an option to disable
WS-Security 1.1 (It is a checkbox with the label "Enable WS-Security 1.1
extensions"). You should select that option to always use Ws-Security 1.0.
As I described in my blog, WS-Security is not the only interoperability
problem that you will have,
there are other problems related to WS-Addressing and the algorithm suite
used for encryption and signing.
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
> Hi Pablo Cibraro,
>
[quoted text clipped - 44 lines]
>> > available
>> > (Interoperability) ?
Loyola stalin - 30 May 2006 15:25 GMT
Hi Poblo..
Thanks for ur knid information..
> Hi,
>
[quoted text clipped - 60 lines]
> >> > available
> >> > (Interoperability) ?