Results 1 to 6 of 6

Thread: [SOLVED] LinkedIn

  1. #1
    dahamsta is offline Senior Member
    Join Date
    Apr 2007
    Posts
    53
    Rep Power
    8

    Default [SOLVED] LinkedIn

    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.

    Code:
    HTTP ERROR 403
    
    Problem accessing /service/proxy. Reason:
    
    FORBIDDEN
    
    Powered by Jetty://

  2. #2
    tdesorbaix is offline Zimlet Guru & Moderator
    Join Date
    Apr 2007
    Location
    Paris, France
    Posts
    367
    Rep Power
    8

    Default

    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 :
    Code:
    zmprov gc yourCOS | grep zimbraProxyAllowedDomains
    If the domain (linkedin) is not allowed, you can add it with the command :
    Code:
    zmprov mc yourCOS +zimbraProxyAllowedDomains YOURDOMAIN

  3. #3
    dahamsta is offline Senior Member
    Join Date
    Apr 2007
    Posts
    53
    Rep Power
    8

    Default

    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:

    Code:
    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?

  4. #4
    tdesorbaix is offline Zimlet Guru & Moderator
    Join Date
    Apr 2007
    Location
    Paris, France
    Posts
    367
    Rep Power
    8

    Default

    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.

  5. #5
    dahamsta is offline Senior Member
    Join Date
    Apr 2007
    Posts
    53
    Rep Power
    8

    Default

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

  6. #6
    LMStone's Avatar
    LMStone is offline Moderator
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,367
    Rep Power
    10

    Default

    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.

    Code:
    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

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •