unsubscribe

2011-10-11 Thread Mark Harrison

RE: Optionally engage WS-Security in the service code

2011-10-11 Thread Okken,Brett
From the client or server perspective? From the client this can be as easy as calling serviceClient.engageModule(“rampart”) when you want to use WS-Security and not calling that when you do not want to use it. I am not sure what a solution would be on the server side. For a given server we eit

Re: Optionally engage WS-Security in the service code

2011-10-11 Thread Sriram Vaidyanathan
Yes , i have done this in the client side. I was looking for if it was possible to do this from the server side. Thanks On Oct 11, 2011, at 5:29 AM, "Okken,Brett" wrote: From the client or server perspective? From the client this can be as easy as calling servic

Re: Optionally engage WS-Security in the service code

2011-10-11 Thread Thilina Mahesh Buddhika
One option is to define two endpoints, one with security and another without security as explained here. http://blog.rampartfaq.com/2009/08/how-to-add-secured-and-non-secured-end.html But in this case, you will have to control access to the non-secured service so that it is not accessible by the