On Mon, 12 Jun 2006 08:30:12 -0400, Rob Richards wrote:
>
> you need to add the following to the LoginServer class on the server side:
> public function authenticate($auth)
> {
> $this->uid = $auth->username;
> $this->pwd = $auth->password;
> }
> }
> this is executed when the SoapServer processes the headers.
>
Yes, that did the trick. Also it solves the situation of not been able to
use the mustUnderstand attribute. See my updated notes.
>
> Am not sure what you mean by the above 2. Have you looked at the
> __setSoapHeaders() method (as of 5.0.5)? It takes an array of SoapHeader
> objects to be added to the message.
>
What I meant was that an automatically generated client from wsdl would
not give you the opportunity to add headers as part of calling a method.
Or is there something I have missed?
>
> Not necessarily. Can use the encryption to protect credentials and/or
> digital signatures to prove identity.
>
But how are you to instruct the clients this information in the WSDL? If
you are doing both server and client this is no problem, but if the
clients are created solely with the information from the WSDL the I see a
problem.
> It is possible. I have been communicating with a .NET service that
> requires wsa, wsu and wsse. The wsse is actually using xml-dsig with
> x509. I am planning on writing about how to do all of this (including
> adding xml-enc) in the near future.
>
Please do. I would must certainly want to read it:-)
> On the server side, it is a bit more complicated and I have been doing
> some research how to make it a little easier to accomplish these on that
> end.
Could you reveal some more information? Maybe write something?
Maybe an idea for a new interface for the ext/soap plugin?
--
Hilsen/Regards
Michael Rasmussen
http://keyserver.veridis.com:11371/pks/lookup?op=get&search=0xE3E80917
--
PHP Soap Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
