rampart

We are implementing WS-Security Policy on our web services with the following framework/module/specification. Apache Axis2 1.6.2 Apache Rampart 1.6.2 WS-Security Policy 1.2(namespace: http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702 ) We are facing the following issues while creating/consuming the service. Axis2 wsdl generation logic ignores <sp:NoPassword/> assertion. After debugging,I realized that it is because of the logic in org.apache.ws.secpolicy.model.UsernameToken (rampart-policy-1.6.2.jar) that expects <sp:WssUsernameToken11 /> ( or <sp:WssUsernameToken10 /> ) to be

I have webservice (server-side) implemented using axis2 in my project. We want to enable WS-security in the existing web services. We are evaluating if apache ramapart module fits our need. Here is our requirement: Basically we have in-house security framework which provides encryption,signature and token generation capabilites. Our in-house security framework basically requires a set of configurations in form of XML and it expose various APIs to do various security operations. Now with above environment, I can think of three possbile solutions:- I can develop an axis2 module around in-house

I have written a client that invokes webservice. My client is: String publisherEPR = "https://abc:8280/services/ProviderPublication"; protected void publicationOpenSession(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { System.out.println("Inside publicationOpenSession"); date = new Date(); namespace = "http://www.openoandm.org/xml/ISBM/"; fac = OMAbstractFactory.getOMFactory(); OMNamespace ns = fac.createOMNamespace(namespace, "ns1"); OMElement result = null; channelURI = request.getParameter("TxtPublisher1ChannelURI"); textfield = request