>From VB I would use the following MS Soap Client low level API calling code:
'--- create SOAP COM objects
Set Connector = CreateObject("MSSoap.HTTPConnector")
Set Serializer = CreateObject("MSSoap.SoapSerializer")
Set Reader = CreateObject("MSSoap.SoapReader")
'--- Prepare the Connector to talk to the SOAP Server. Note that the
"SoapAction" data is not
'--- consequential on the server side so the contents can be anything at
all - It is a good idea
'--- to set it to the URI and Method name for easier identification when
you are debugging and reading
'--- the SOAP messages. NOTE: Axis requires a SoapAction (hence the fact
that we cannot use the high-level API)
Connector.Property("EndPointURL") = URL
**** I've tried all combinations of the following 4 lines to get the
UserCode and Password across ****
'Connector.Property("AuthUser") = "xander"
'Connector.Property("AuthPassword") = "123456"
'Connector.Property("ProxyUser") = "pxander"
'Connector.Property("ProxyPassword") = "p123456"
Call Connector.Connect
Connector.Property("SoapAction") = URI & "#" & aMethod
Call Connector.BeginMessage
... and so on...
You can see where I try to set the AuthUser and AuthPassword, etc - there is
no way I can find to read this information at the Server side to
authenticate. I assume that I will be able to write some server side Java to
check and authenticate this username and password? I'm also just starting
with Axis so I might be missing something very simple here.
Thanks
Xander
----- Original Message -----
From: "Phillip Rhodes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 26, 2003 2:49 PM
Subject: Re: Authentication woes
> What do you mean by authentication not working?
>
> Axis is able to use the servlet container's session tracking mechanism, so
> it should return a cookie to the client. Can you run an http sniffer and
> see if the cookie is being returned to your client? Is the client sending
> the cookie in the http request that it sends?
>
> I am new to axis, (as you can tell from my bone-head responses), but if
> the authentication is handled outside the realm of the xml documents that
> are in the transport, and are handled via the cookies in the http
> response/request, than the previous point would be a good place to start
> looking.
>
>
>
>
> At 02:27 PM 3/26/2003 +1200, you wrote:
> >I've been having problems getting authentication to work from non-Java
> >clients (e.g. VB6, etc). I was wondering whether it would be so silly to
> >ignore the normal authentication mechanism and simply included a UserName
> >and Password set of parameters in each and every webservice method that
is
> >exposed. This would provide for any easy no-nonsense authentication
> >mechanism that will work for any client.
> >
> >Any thoughts appreciated...
> >
> >Thanks
> >Xander
>
>
