soap api: strange behavior after update

[yodog]

zimbra: Release 8.8.15_GA_3869.RHEL7_64_20190917004220 RHEL7_64 NETWORK edition, Patch 8.8.15_P4.

i have a few scripts (mostly php) that need an admin token to work.

everything was working fine until applying the latest patch (8.8.15_P4) last week.

every script dependent on authRequest (the request) and authToken (the response) broke.

after hours of debugging, i found out that the parameter 'account' does not work anymore, returning 'system failure: java.lang.NullPointerException' in the response

replacing it with 'name' fixed the error.


is this the expected behavior or a bug?

also, if this is expected, where can i find the 'breaking changes' docs?


this broke our production environment and i need to be sure its the only thing that needs to be fixed.

[L. Mark Stone]

If you haven't already, I would absolutely open a Support Case for this.

Keep us all updated?

All the best,
Mark

[yodog]

just to let you all know, the Patch 6 does not fix this problem.

i had to downgrade zimbra-openjdk in the mailbox to get it to work again

Code: Select all

rpm -Uvh --force --nodeps $(repoquery --location zimbra-openjdk-11.0.2-1zimbra8.8b1.el7.x86_64)

[L. Mark Stone]

just to let you all know, the Patch 6 does not fix this problem.

i had to downgrade zimbra-openjdk in the mailbox to get it to work again

Code: Select all

rpm -Uvh --force --nodeps $(repoquery --location zimbra-openjdk-11.0.2-1zimbra8.8b1.el7.x86_64)

This _may_ be a known session cookie bug that impacted one of my customers. The fix will be in Patch 7 I am told, but until then you can try this workaround:

Code: Select all

zxsuite admin doStopService logging

If you restart mailboxd, you'll need to stop the logging service again. And while the service is stopped, the Admin NG reports will be incomplete or empty.

Hope that helps; please let us know if this works for you?

All the best,
Mark