Ztalk 403 Error eturned when requesting middleware lib.js

Revision as of 12:27, 14 August 2017 by Nbhagwat (talk | contribs) (Created page with "===<h1>Ztalk 403 Error returned when requesting middleware_lib.js </h1>=== <hr> <br. <h2>Problem:</h2> 403 Error returned when requesting middleware_lib.js <h2>Solution:</h...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
===

Ztalk 403 Error returned when requesting middleware_lib.js

===

<br.

Problem:

403 Error returned when requesting middleware_lib.js

Solution:

When the GET request for https://<Zimbra-URL>/service/proxy?target=...returns 403 (Forbidden) it indicates that the proxy servlet is not allowed to access the target.

So please check if the user's domain (further refered to as "yourdomain.tld") is set as value in zimbraProxyAllowedDomains for the account's COS which is getting this error :

  • Login as user zimbra to the Zimbra server and check if the domain is listed when executing :
zmprov gc <account's COS> zimbraProxyAllowedDomains
  • Expected result :
# name <account's COS>
zimbraProxyAllowedDomains: *yourdomain.tld
...
  • In case "*yourdomain.tld" is not returned, it must be set via
zmprov mc <account's COS> zimbraProxyAllowedDomains "∗yourdomain.tld"

Symptoms

https://<Zimbra-URL>/service/proxy?target=... returns 403 (Forbidden)

Reasons and prerequisits

zimbraProxyAllowedDomains not configured for account's COS


"Raunaq Malik"

<rmalik@zimbra.com>

Jump to: navigation, search