CAn you provide your deployment parameters? Even better if you could
show the message (using e.g tcpmon to monitor it).

Regards,
Werner

Sidhu Kiran IT312 wrote:
> I am trying to test with .NET 2.0 client , WSE 3.0 and I am running into
> problems :(
>  
> I am getting the following exception (I googled on this and installed
> local_policy.jar and Us_export_policy.jar as suggested by some posters,
> but it didn't help )
>  
> 
> org.apache.ws.security.WSSecurityException: Cannot encrypt/decrypt data;
> nested exception is:
> 
> java.lang.SecurityException: Unsupported keysize or algorithm parameters
> 
>     -----Original Message-----
>     *From:* Kosuru, Giri [mailto:[EMAIL PROTECTED]
>     *Sent:* Monday, March 06, 2006 10:55 AM
>     *To:* [email protected]; [EMAIL PROTECTED];
>     [EMAIL PROTECTED]
>     *Subject:* WSS4J interoperability
> 
>     Hi all,
> 
>      
> 
>                 We implemented WSS4J for securing one of our Web
>     Services (Uses apache Axis). As the implementation seems to be
>     simple and straight forward for basic requirements, we are planning
>     to make it as a standard for other java/j2ee applications to
>     implement WSS4J. But we are concerned about the interoperability of
>     WSS4J with others, particularly .NET. The WSS4J web site says it is
>     interoperable. But did any body did integrate WSS4J with .NET
>     before? If yes, what are your experiences? Is it safe to assume
>     interoperability and go ahead and make it a standard? You
>     experiences will help me a lot on making a good decision. Mean while
>     I will also try to test and if I find some thing I will share with you.
> 
>      
> 
>     Thanks
> 
>     Giri Kosuru
> 
>      
> 
>      
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to