[cvs] [Wiki] changed: ExternalClientsHowTo

[Wiki Guest]

guest [81.168.10.73]  Fri, 27 Feb 2009 17:33:46 -0500

Modified page: http://wiki.horde.org/ExternalClientsHowTo
New Revision:  1.4
Change log:  Added a note about RPC and the Shibboleth auth driver not  
being compatible

@@ -27,7 +27,9 @@
  Several generic RPC interfaces exist in Horde, at the time of this  
writing XML-RPC, SOAP, and JSON. These can be used to access the  
external API of Horde and its applications and are rather targeted at  
developers. But there exists a ((PhpgwHowTo|wrapper around the XML-RPC  
interface)) that is compatible to the RPC interface of  
**[http://www.phpgroupware.org/  
phpGroupWare]/[http://www.egroupware.org/ eGroupWare]**. At least one  
client **(Kontact)** supports this interface. It hasn't been tested  
much though.

  Of course you can combine any of the scenarios mentioned here. You  
could use Horde as a frontend for a Kolab server and as a SyncML  
server for your **PDAs** and **phones** at the same time. Or you can  
use the Kolab server as a groupware backend, but add more address  
books from your company's LDAP or Active Directory servers, etc.

-+++ Authentication Caveat
++++ Authentication Caveats

  The above methods all use the rpc.php entry point to horde, which in  
most cases uses basic HTTP authentication to authorize access. This  
may not work out of the box when PHP is run in CGI mode. Please see  
HTTPAuthHowTo for a workaround.
+
+If you have configured Horde to use Shibboleth as an authentication  
method then the RPC interface will fail as Horde will have no means to  
authenticate the user with the supplied HTTP authentication  
credentials (no _authenticate method in the Shibboleth driver).  
Shibboleth is designed for web browser based applications and hides  
the authentication part from Horde, providing just a trusted session  
and attribute data about the externally authenticated user.