Hi,
Two questions: Introduction: I use Rampart 1.5.0 and Axis2 1.5.1. The SOAP server is WCF and it works ok. The policy is embedded in the SOAP and the AXIS2 client works after engaging Rampart without specifying a policy file. The authentication is done on the SOAP server. For each client request the username and password is inserted into the ServiceClient's Options object. The strange thing is that Rampart also authenticates the username and password. Question 1) Why does Rampart do its own authentication? I believe Rampart is needed in order to interpret the WS-Security SOAP messages - but I don't need it to do anything else. Question 2) Really what I would like to do is leverage Tomcat's login features and still authenticate via the current system. I don't want to have to import all the authenticated users to the tomcat database and would prefer not having to implement something new on the SOAP server. I realise this might be more appropriate for the tomcat list. Any ideas? Cheers, James Infoshare Ltd Millennium House 21 Eden Street Kingston upon Thames Surrey KT1 1BL United Kingdom Phone: + 44 (0) 20 8541 0111 Support: + 44 (0) 20 8481 4760 Web: www.infoshare-is.com E-mail: i...@infoshare-is.com Infoshare Ltd is registered in England and Wales. Registered Office as above. Registered Number 2877612 VAT Number GB 678 1443 10 The content of this e-mail (and any attachment to it) is confidential. Any views or opinions do not represent the views or opinions of Infoshare Ltd. If you have received this e-mail in error please notify the sender and delete it. You may not use, copy or disclose the information in any way. Infoshare Ltd monitors incoming and outgoing e-mails. Please consider the environment. Do you really need to print this email?
