zimbra PHP-SOAP API (with GET Params)

[gunthor]

I've made a simple API to controll zimbra with for PHP or even GET params. It isn't full ready or tested yet, but the main tasks works fine now. Maybe the one or other want to extend, test or improve it (or translate it, currently its written and commented in German...)

theres also no authentification now (e.g. md5), only an restriction for local Ip's.

so long, have fun

Günther

p.s.: you shouldn't forget .htaccess

[stiller]

Excellent work. How does this relate to the PHP class in the sticky?

@Moderators: Perhaps make this a sticky as well?

@Zimbra: Considering the amount of work and discussions concerning PHP/Perl/Other classes for zimbra SOAP/REST communication, perhaps it would be a good idea to collect those in a wiki, documenting the differences, improvements, problems, etc. If that hasn't been done already.

Delivering a complete SDK with these classes would be even better of course. This would greatly reduce the learning curve for new developers.

[phoenix]

Originally Posted by stiller

Excellent work. How does this relate to the PHP class in the sticky?

@Moderators: Perhaps make this a sticky as well?

It should go in the wiki, it's a Community resource and is available to anyone to add their information to it.

[gunthor]

yep, the documentation has to be done, unfortunately i've no time at the moment... a documentation is written once, but read oft-times...

a short introduction can I give you now:

$zimbraction=new zimbraaction(); (also not named in convention, as i see now... ) is the controller for the actions, coded in the GET-cmd string. In his constructor, it makes an instance of ZimbraSoap API $this->z=new zimbraSoapApi().

The controller has this main functions:

$zimbraction->dofixedarglength($cmd, $cmdarray);
$zimbraction->dovararglength($cmd, $cmdarray);

for admin controlls (admin get logged in), segmented for defined params, and dynamical params (afterward i see, it's not well structured! there is much to rework!)

$zimbraction->douserfixargs($cmd, $cmdarray);
for actions, which the user must do (e.g. search folder or something). the user get preAuth.

$zimbraction->getnewmails($cmd, $cmdarray);$zimbraction->cal($cmd, $cmdarray); $zimbraction->newmsg($cmd, $cmdarray);
=> user functions, which aren't ready now, but working fine. they must be adjust and extend for useful working.

zimbraSoapApi:

divided into 3 main parts: admin, user and upload actions. The user/admin get automatically logged on; it uses the cached auth-tokens and times. If they are out of time or incorrect, they get renewed. The pear XML-serializer makes an array out of the xml response.

Upload is developed with curl. An image with web-url get uploaded into a local directory.

hope, you could help me to make it much more usable!

regards

gunthor

[gunthor]

Hi,

i tried to structure the SOAP Kit and modulize it, so that it can be extended easily.
It's quite easier as before, and no there is also a Shell-feature, where zmpov commands (or all other linux commands) can be used.

I also began to documentate the whole thing in english.

Not ready yet, but maybe you can give me feedback or improve/add some sections. At the moment I try to improve the error handling and logging classes....

It would be great, if you'll get part of this project!

gunthor's zimbraControl at gunthor - GitHub

so long, enjoy life


Günther