(C) 2001-2004 Miles Lott milos@groupwhere.org August 23, 2001 and December 29, 2003 additions made September 3, 2001. This document is very preliminary, but describes a working system. Authentication for user logins is handled internally no differently than for the typical eGroupWare login via web browser. Server logins, added for XML-RPC and SOAP, are only slightly different. For either protocol, user and server login and authentication and subsequent requests are handled by their respective server apps, xmlrpc.php and soap.php. A server is identified by a custom HTTP header, without which a normal user login will be undertaken. A client or server sends the appropriate XML-RPC or SOAP packet containing host, user, and password information to the phpgw server. The server then assigns a sessionid and key, which is returned to the client in the appropriate format. Our current method for authenticating requests after successful login is via the Authorization: Basic HTTP header to be sent by the client or requesting server. The format of this header is a base64 encoding of the assigned sessionid and kp3 variables, seperated by a ':'. Further security may be obtained by using SSL on the client and server. In the future, we may encrypt/descrypt the data on either end, or at least provide this as an option. The sessionid and key variables will make this possible, and relatively secure. The first request a client will make is the system.login method. Here is a sample of a server login packet in XML-RPC: ]]> ]]>system.login ]]> ]]> ]]> ]]>server_name ]]>my.host.name ]]> ]]>username ]]>bubba ]]> ]]>password ]]>gump ]]> ]]> ]]> ]]> ]]> And the same in SOAP: ]]> ]]> ]]>my.host.name ]]>bubba ]]>gump ]]> ]]> ]]> ]]> The same style of packet would be required for a user/client login. A successful login should yield the following reply: ]]> ]]> ]]> ]]>sessionid ]]>cf5c5534307562fc57915608377db007 ]]> ]]>kp3 ]]>2fe54daa11c8d52116788aa3f93cb70e ]]> ]]> ]]> ]]> ]]> ]]> And a failed login: ]]> ]]> ]]> ]]>GOAWAY ]]>XOXO ]]> ]]> ]]> ]]> ]]> ]]> eqweqw Logout: ]]> ]]>system.logout ]]> ]]> ]]>sessionid ]]>ea35cac53d2c12bd05caecd97304478a ]]> ]]>kp3 ]]>4f2b256e0da4e7cbbebaac9f1fc8ca4a ]]> ]]> ]]> ]]> ]]> ]]> Logout worked: ]]> ]]> ]]> ]]>GOODBYE ]]>XOXO ]]> ]]> ]]> ]]> ]]> ]]> Once a successful login return packet has been received and sessionid/kp3 have been extracted, every subsequent packet sent to the egroupware server must be preceded by an Authorization header. Here is a sample header: The longish string is a base64 encoding of the $sessionid . ':' . $kp3. For now this is our only supported authentication method. Additional methods would probably also affect the methodCalls. This is certainly open to discussion. Following is a typical request for some contact data: ]]> ]]>addressbook.boaddressbook.read_entries ]]> ]]> ]]> ]]>start ]]>1 ]]> ]]>limit ]]>5 ]]> ]]>fields ]]> ]]>n_given ]]>n_given ]]> ]]>n_family ]]>n_family ]]> ]]> ]]> ]]>query ]]> ]]> ]]>filter ]]> ]]> ]]>sort ]]> ]]> ]]>order ]]> ]]> ]]> ]]> ]]> ]]> ]]> Successful response: ]]> ]]> ]]> ]]> ]]>0 ]]> ]]>id ]]>1 ]]> ]]>lid ]]> ]]> ]]>tid ]]>n ]]> ]]>owner ]]>500 ]]> ]]>access ]]>private ]]> ]]>cat_id ]]>1 ]]> ]]>n_given ]]>Alan ]]> ]]> ]]> ]]>1 ]]> ]]>id ]]>2 ]]> ]]>lid ]]> ]]> ]]>tid ]]>n ]]> ]]>owner ]]>500 ]]> ]]>access ]]>private ]]> ]]>cat_id ]]>1 ]]> ]]>n_given ]]>Andy ]]> ]]> ]]> ]]> Unauthorized access attempt returns: ]]> ]]> ]]>UNAUTHORIZED ]]> ]]> ]]> ]]> Documenting every single call will be difficult, but should be done. In leiu of this, please see the class.bo{APPNAME}.inc.php files in each application/inc directory in the egroupware cvs. In this file will be a list_methods() function, which returns the information to the server about input/output structure for each call. If the file does not have this function, then it is not yet workable via this interface. As for the actual functions, they are also in this file. Generally, they will all accept associative array input and return same, but not always. This code is in flux, have fun.