Bugzilla Zimlet Configuration Not Working

[Mercer]

I am configuring the Bugzilla Zimlet using this process. Am I forgetting something? The configuration changes are ignored. I have already installed the zimlet using zmzimletclt install.

zimbra@server:~/conf$ zmzimletctl getConfigTemplate /opt/zimbra/zimlets-extra/com_zimbra_bugz.zip > bugz_zimlet-config.xml

I modify the file as follows:

<zimletConfig name="com_zimbra_bugz" version="1.0">

        <global>

                <property name="url">http://mybugzilla.mydomain.com/bugzilla/show_bug.cgi</property>

        <property name="allowedDomains">*.mydomain.com</property>

    </global>

</zimletConfig>

Then, I tell zimbra to use it:

zimbra@server:~/conf$ zmzimletctl configure bugz_zimlet-config.xml 
[] INFO: Installing Zimlet config for com_zimbra_bugz

But no matter how many times I restart tomcat/zimbra/the server, it always hits bugzilla.zimbra.com instead of my local bugzilla server.

[mmorse]

-sometimes it's better to just unzip>modify>re-zip
-clean out/delete the com_zimbra_bugz folder in /opt/zimbra/tomcat/webapps/service/zimlets/

[Mercer]

I unzipped it, edited the com_zimbra_bugz.xml, then re-zipped and re-deployed it. However after doing so, it would just hang on 'fetching...' forever. Digging through the tomcat logs, I found this zimlet using the proxy service (/service/proxy), so this needed ran as well:

zmprov mc default zimbraProxyAllowedDomains "*.mydomain.com"

Now it is working perfectly.

I noticed before I changed it, that field defaulted to *.zimbra.com. Is proxying for *.zimbra.com needed for the proper functioning of Zimbra? What is the proper delimiter for adding multiple domains there?

[mmorse]

in the zip-in the file config_template.xml it looks like:
<zimletConfig name="com_zimbra_zimletname" version="1.0">
<global>
<property name="allowedDomains">*.domain.com,*.domain2.com</property>
</global>
</zimletConfig>

*.domain.com, *.domain2.com

you can also pretty much place wild card's anywhere-like:
*.*.org , *.edu, *.net
zimbra.*.com
or just * to allow any domains/addresses

[ei99045]

Comma delimiter doesn't work when used with zmprov.
The default COS has multiple zimbraProxyAllowedDomains properties, not a single one comma-delimited.

AFAIK it's not possible to do the same using zmprov. How can I add another zimbraProxyAllowedDomains to an existing COS?

[mmorse]

hm I always just assumed it worked with "domain.com, *.domain2.com"
I gather your against using *, I don't have time to test right now, but try +zimbraProxyAllowedDomains?
If you modify the .xml then redeploy (and as discussed below only probably just to the default cos) does it copy over with zmzimletctl acl cos grant?
Or if you zmzimlet configure & apply the .xml after it's deployed/enabled in the specified cos, will it grab the correct zimbraProxyAllowedDomains?

someone came across:

Originally Posted by riogd

Now the rather large problem, and what makes this seem even more like a bug, is that although the config isn't applied to
non-default COS's, re-deploying the Zimlet wipes out the zimbraProxyAllowedDomains for all non-default COS's. So each time you redeploy the Zimlet you have to go and make that manual change. This is why I was constantly getting 403's, my manual settings kept getting wiped without my knowing it.

and in another thread (same person though)

Originally Posted by riogd

I suspect I may have found the problem but I have yet to test. I must also note that I am using the AdminUI for deployment and enabling in the COS's.
Non-default COS's do not get the config_template applied to it, which seems quite possibly like a bug, more info on that here (in summary even though the allowedDomains isn't automatically applied to non-default COS's, if you add them manually they are automatically wiped while re-deploying. I suspect similar oddity is happening with properties in the config_template for non-default COS's).

If it's really failing to apply the config_template to other cos's, maybe it's time that someone makes this into a bug (I can't find one open on it-though who knows what they labeled it...)

Also, Bug 11180 - Add a pane for adding zimbraProxyAllowedDomains

I'll point josh & riogd at this thread as well

other threads:
/forums/zimlets/5433-problem-reading-config_template-xml-js.htm
/forums/zimlets/11283-proxy-service-alloweddomains.html
/forums/zimlets/5780-zimlet-403-via-proxy-help.html

[ei99045]

I'm in an early deployment stage so I got myself off the hook by erasing the non-default COS, "zmzimletctl configure" with the appropriate domains and then duplicating the default COS to create the non-default COS (differences are small and easy to remember).

Thanks for the pointers to the other threads and to the enhancement request (i'm voting for that one).