documentation inaccessible for SOAP API

Have a great idea for extending Zimbra? Share ideas, ask questions, contribute, and get feedback.
Post Reply
gromit08
Posts: 9
Joined: Sat Sep 13, 2014 2:53 am
ZCS/ZD Version: 8.7.5_GA_1764.RHEL6_64_201703140325

documentation inaccessible for SOAP API

Post by gromit08 »

After a recent update, much of the items setup to use the SOAP API are not working. (SSO, unified password changes, automated account creation synced with ADFS, etc, etc)

The SOAP API documentation we've found:
https://wiki.zimbra.com/wiki/SOAP_API_R ... with_ZCS_8

fails with XML errors.
i.e. For zcs 8.7.0, you are brought to this page:

https://files.zimbra.com/docs/soap_api/ ... index.html

Selecting any item, i.e. zimbraAdmin, gets an error like this:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>BD2102FBDED5610A</RequestId><HostId>Qc+tLx+3UDKkAqN8KelLnJubWeEFr+2jRW7xmvyCzBR8UpC+3A+m6/FgFFIFjDtN5iw5EOxV4Pg=</HostId></Error>

This post: viewtopic.php?f=17&t=62615
refers to changes made to "trying to migrate the SOAP request handlers to use JAXB objects".

Is there any accessible documentation for the SOAP API and the changes introduced by these packages:

zimbra-apache-components-1.0.1-1zimbra8.7b1.el6.x86_64
zimbra-core-components-1.0.3-1zimbra8.7b1.el6.x86_64
zimbra-mariadb-10.1.25-1zimbra8.7b1.el6.x86_64
zimbra-mariadb-libs-10.1.25-1zimbra8.7b1.el6.x86_64
zimbra-openjdk-1.8.0u144b01-1zimbra8.7b4.el6.x86_64
zimbra-openssl-1.0.2l-1zimbra8.7b2.el6.x86_64
zimbra-openssl-libs-1.0.2l-1zimbra8.7b2.el6.x86_64
zimbra-php-5.6.31-1zimbra8.7b2.el6.x86_64
zimbra-spell-components-1.0.1-1zimbra8.7b1.el6.x86_64
zimbra-store-components-1.0.1-1zimbra8.7b1.el6.x86_64

Thank you
User avatar
msquadrat
Advanced member
Advanced member
Posts: 183
Joined: Mon Oct 14, 2013 10:09 am

Re: documentation inaccessible for SOAP API

Post by msquadrat »

Those are actually AWS S3 errors you're seeing there. Looks like somebody screwed up the rights there. I hope Jorge or somebody else from the team fixes this soon.

You can also build the SOAP documentation from the sources but I don't have the correct commands at hand right now.
Post Reply