I believe that the first problem at hand is using ?wsdl over https. The tools client can't be a big deal, insofar as users can get around it with 'wget'. At least, that's how I read Dan's comments about a possible approach to some code.
On Wed, Jul 23, 2008 at 11:52 PM, Glen Mazza <[EMAIL PROTECTED]> wrote: > > > dkulp wrote: >> >> We could extend it for this case to allow something like: >> >> <http:conduit >> name="https://my.server.com/webservices/services/MyService?wsdl";> >> >> > > Although I may be way off in what is being discussed here, I'm not sure if > that will work, because the servlet container won't let you access the > servlet until you have provided the basic auth username and password, so any > servlet-logic such as the above would never be activated, correct? I > believe there's a Java Authenticator class that can be used instead: > http://www.nabble.com/Re%3A-How-to-pass-authetication-to-a-web-service...-p16686141.html > > Again, this is assuming (20% chance) that I'm talking about what you're > talking about. > > Glen > > -- > View this message in context: > http://www.nabble.com/https-for-wsdl-tp18609319p18625023.html > Sent from the cxf-dev mailing list archive at Nabble.com. > >
