User authentication

--===============1937997420==
Content-Type: multipart/alternative; 
	boundary="----=_Part_3335_31448095.1143423478301"

------=_Part_3335_31448095.1143423478301
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello

I'm very new to PHP, taking it up primarily to use the XML-RPC package.

I would like to protect most of my rpc methods such that they will only
execute when called by an authorised user. I'm not quite sure how to go
about authentication though.

Does anybody have a best practices guide on how to achieve client
authentication? Is it best to use http basic auth and check credentials on
each method call? Or is there some inherent PHP support for sessions that
can be used?

Yours confusedly,
Jem

--
http://www.loftinspace.com.au/jem

------=_Part_3335_31448095.1143423478301
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello<br><br>I'm very new to PHP, taking it up primarily to use the XML-RPC=
 package.<br><br>I would like to protect most of my rpc methods such that t=
hey will only execute when called by an authorised user. I'm not quite sure=
 how to go about authentication though.
<br><br>Does anybody have a best practices guide on how to achieve client a=
uthentication? Is it best to use http basic auth and check credentials on e=
ach method call? Or is there some inherent PHP support for sessions that ca=
n be used?
<br><br>Yours confusedly,<br>Jem<br clear=3D"all"><br>-- <br><a href=3D"htt=
p://www.loftinspace.com.au/jem">http://www.loftinspace.com.au/jem</a>

------=_Part_3335_31448095.1143423478301--

--===============1937997420==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
phpxmlrpc mailing list
[email protected]
http://lists.usefulinc.com/cgi-bin/mailman/listinfo/phpxmlrpc

--===============1937997420==--