[SOLVED] LinkedIn

[dahamsta]

When I try to authorise Linked in via the "Go To LinkedIn" button, I get the following error dialog.

Is zimbra-proxy the problem? I don't think I have it installed, didn't think it was needed for non-core operations.

HTTP ERROR 403

Problem accessing /service/proxy. Reason:

FORBIDDEN

Powered by Jetty://

[tdesorbaix]

The proxy used by zimlets is automatically installed.
It is not the zimbra-proxy.

You can see the allowed domains for the proxy in the CLI :

zmprov gc yourCOS | grep zimbraProxyAllowedDomains

If the domain (linkedin) is not allowed, you can add it with the command :

zmprov mc yourCOS +zimbraProxyAllowedDomains YOURDOMAIN

[dahamsta]

Thanks tdesorbaix. Those hostnames looked familiar to me, I was able to add *.linkedin.com via COS > Advanced > Proxy Allowed Domains in the Admin Console, where they were exposed in v7.

Shouldn't this hostname have been added by Zimbra, when LinkedIn is a default Zimlet?

Also, any comment on the other hostnames currently set:

zimbraProxyAllowedDomains: *.yimg.com
zimbraProxyAllowedDomains: *.yahoo.com
zimbraProxyAllowedDomains: *.maxmind.com
zimbraProxyAllowedDomains: *.csgnetwork.com
zimbraProxyAllowedDomains: *.yahooapis.com
zimbraProxyAllowedDomains: *.linkedin.com

In particular, why are maxmind and csgnetwork in there? Maxmind I know, presumably that's for some kind of geoip, but csgnetwork.com?

[tdesorbaix]

Yes, the domain should be added by default with the configuration file "config_template.xml" in the zimlet.
Maybe you had an error during the installation.

For maxmind and csgnetwork, they come from the com_zimbra_local zimlet.

[dahamsta]

No errors, but I've fixed it now anyway. Thanks very much for your help.

[LMStone]

This issue comes up every now and then so thought I'd post the underlying problem and solution...

The attribute zimbraProxyAllowedDomains appears multiple times in each COS (Class of Service). Based on a COS creation template, the attributes are added to a COS at the time the COS is created.

Periodically, Zimbra releases a new zimlet or some other functionality that expands the number of zimbraProxyAllowedDomains in newly-created COS's. But, existing COS's never get updated automatically by Zimbra, even during Zimbra upgrades.

If the attribute is missing, you get the OP's Jetty error.

As of Zimbra 7.1.3, here is the list of zimbraProxyAllowedDomains for a newly-created COS.

zimbraProxyAllowedDomains: *.googleusercontent.com
zimbraProxyAllowedDomains: api.tr.im
zimbraProxyAllowedDomains: *.smartsheet.com
zimbraProxyAllowedDomains: api.bit.ly
zimbraProxyAllowedDomains: *.tweetmeme.com
zimbraProxyAllowedDomains: *.yimg.com
zimbraProxyAllowedDomains: *.joedeveloper.net
zimbraProxyAllowedDomains: localhost
zimbraProxyAllowedDomains: *.broadsoft.*
zimbraProxyAllowedDomains: *.salesforce.com
zimbraProxyAllowedDomains: twitter.com
zimbraProxyAllowedDomains: *.calcxml.com
zimbraProxyAllowedDomains: *.webex.com
zimbraProxyAllowedDomains: *.twitter.com
zimbraProxyAllowedDomains: *.yahoo.com
zimbraProxyAllowedDomains: *.digg.com
zimbraProxyAllowedDomains: *.yahooapis.com
zimbraProxyAllowedDomains: *.google.com
zimbraProxyAllowedDomains: xsp.eng.broadsoft.com
zimbraProxyAllowedDomains: *.socialcast.com
zimbraProxyAllowedDomains: *.sforce.com
zimbraProxyAllowedDomains: *.linkedin.com
zimbraProxyAllowedDomains: ssutar.*
zimbraProxyAllowedDomains: *.ihs.broadsoft.com
zimbraProxyAllowedDomains: *.flickr.com
zimbraProxyAllowedDomains: *.facebook.com
zimbraProxyAllowedDomains: *.zimbra.com
zimbraProxyAllowedDomains: *.maxmind.com
zimbraProxyAllowedDomains: *.xdp.broadsoft.com
zimbraProxyAllowedDomains: *.csgnetwork.com

Any that are missing from your existing COS's can be added via the command stated earlier in this thread.

Hope that helps,
Mark