Microsoft way to do it does not work all the time. Tested, and their documentation has many flaws.
Let's get you example:
>set SoapClient = createobject("MSSoap.SoapC
>SoapClient.ConnectorPrope
>SoapClient.mssoapinit("ht
CurrencyExchange.wsdl")
If you'll try it (at least in C++) you'll not be able to set any connector property prior to soapclient initialization (i.e. mssoapinit call). It will fail with 'object not initailized'.
But I think you did not got my problem right: I just want to call mssoapinit with a remote wsdl file as parameter. What you say is about invoking (calling) functions from the webservice afterwards. The question is HOW to make mssoapinit to get the proxy authentication params (as it uses the IE proxy settings, and the user/pass are not explictly set).
I am willing to "upgrade" to MSSOAP 3.0 (even if it requires MSXML 4.0) if that will solve my problem.
Main Topics
Browse All Topics





by: drichardsPosted on 2004-12-24 at 05:46:17ID: 12899092
Here's how Microsoft says to do it. Looks like there are additional properties "ProxyUser" and "ProxyPassword" that you can set. Notice the caveats at the end as well.
---------- ---------- --
lient") ty("UsePro xy") = true p://servic es.xmethod s.net/soap /urn:xmeth ods- ty("ProxyS erver") = "secureproxy" ty("ProxyP ort") = 80 ty("ProxyU ser") = "username" ty("ProxyP assword") = "password"
--------------------------
Proxy Authentication
A proxy server may require you to authenticate yourself before the connection goes through. For example, it may be used to restrict use of the Internet from within a corporate intranet. Proxy servers may use all authentication schemes discussed above. Microsoft SOAP Toolkit 2.0 allows you to specify a user name and password for proxy authentication:
set SoapClient = createobject("MSSoap.SoapC
SoapClient.ConnectorProper
SoapClient.mssoapinit("htt
CurrencyExchange.wsdl")
SoapClient.ConnectorProper
SoapClient.ConnectorProper
SoapClient.ConnectorProper
SoapClient.ConnectorProper
Quote = SoapClient.GetQuote()
If your Proxy requires NTLM authentication, you may omit user name and password, causing it to use the current logon credentials. If you need to specify a domain name for proxy NTLM authentication, add "DOMAIN\username" as for server authentication.
Limitations. Microsoft SOAP Toolkit 2.0 does not support connection to a server that requires authentication through a proxy that also requires authentication. Additionally, SSL connections through a proxy that requires authentication will not work on Windows 2000 and Windows NT 4.0.