It might require more effort than your time permits, so I would say disable the soapmonitor module until you need it.
Since this really has nothing to do with axis2 - you just want to password protect a url - there really is nothing to integrate. The way I'd do it - acegi - is far beyond the scope of axis2 I'd imagine. Robert On 6/20/07, Gul Onural <[EMAIL PROTECTED]> wrote:
How easy is this? We are about to deliver the product for trial and I cannot make to much change right now. Are you planning to integrate this solution to next version of Axis2 ? Gul ------------------------------ *From:* robert lazarski [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, June 20, 2007 8:55 PM *To:* [email protected] *Subject:* Re: How to password protect access to SOAPMonitor I tend to put basic auth on the soap monitor using acegi - a security framework that requires spring, but doesn't need any axis2 / spring integration. If you decide to go that route I can help you implement it as its pretty easy once you know how to do it. Robert On 6/20/07, Gul Onural <[EMAIL PROTECTED]> wrote: > > Hi, > > I noticed that the SOAPMonitor is not protected with userId/password. If > somebody knows the url of the service, > he can then launch the SOAPMonitor and see the messages coming back and > forth. > > Is there a way to password protect the SOAPMonitor, or we just have to > take it out from our production system? > > Gul >
