This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Web Services and the fly likes Dynamically add ws-security to a service Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Dynamically add ws-security to a service" Watch "Dynamically add ws-security to a service" New topic
Author

Dynamically add ws-security to a service

Yogendran Gopalakrishnan
Greenhorn

Joined: Jan 16, 2012
Posts: 3
hi all,


I have a service where we have implemented ws-security with certificate (issuer name and serial number). Rampart is used for the security configuration and the configurations for the same is in the services.xml like below,



It works great without issues. But some of our customers would like for the ws-security to be turned off when they dont need it. Now, they do not want to be going in and modifying the code to remove the ws-security assertions in the services.xml and moreover it would be inside the WAR file. Is there a way to programatically turn off the ws-security settings and not have the service go through security? Dynamic rampart configuration is an option I am exploring (and having quite some trouble with --> see my thread --> http://www.coderanch.com/t/564573/Web-Services/java/Issues-dynamically-configuring-rampart-configuration). Apart from the dynamic rampart configuration, is there any other way that I can get this achieved? Suggestions please.

Regards,
Yogi
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Dynamically add ws-security to a service
 
Similar Threads
WSDoAllReceiver: security processing failed (actions mismatch)
CryptoFactory: Cannot load properties: client.properties, anyone???
returnMessageContext is getting set to null why?
Rampart encrypting options: I can't encrypt parameters
Issues in dynamically configuring rampart configuration with axis2