Alfresco Zimlet (Beta)

[nowrap]

Hello,
i use alfresco with https only. Is there any chance to add the protocol to the connection settings?

i tried a http rewrite rule from http to http without success.

regards
.nowrap

[nowrap]

hello,
i am running alfresco with https and can get the zimlet to work with this scenario.

I added a redirect from http to https. but this also don't work. i am getting a 404 error from service/proxy. Within the target parameter the alfresco url is still http but now with port 443 added.

Is there any chance to run the zimlet with https?

regards
.nowrap


// edit
I opend the zip-file, replaced within the org_alfresco_zimbra.js all http:// with https:// and restartet zimbra.
Now it's working.

[arash.kaffamanesh]

Is there any updates to this thread? I'm still not able to get the Alfresco Zimbra integration to work. I'm using Zimbra 5.0.13 and Alfresco Labs Stable 3.0.0, after deploying the zimlet on zimbra and importing the webscripts through alfresco's webclient I'm now able to connect to Alfresco, but in the "About Alfresco" Dialog no infromation about the "Server Version", Server Edition", User Id and User Name are displayed and by trying to add attachments through the "Alfresco Documents" tab only the company home node is displayed and can't get expanded.

And if I try to save an attachment from an email to Alfresco the dialog box claims that "Upload to Alfresco suceeded", but the attachment is not shown in Alfresco's Webclient, so I think this amazing zimlet is still in beta phase or it works only with Alfresco Enterprise ;-) ?

Any ideas?

Thanks in advance for any hints.

[triveros]

same here,
deployed this on ZCS 6.0.0 and Alfresco Community 3.2 stable.
it's all installed properly (using files from page 3), but I cannot attach alfresco docs to a new mail (hangs in there forever), and I cannot save attached files to alfresco (it says success, but nothing happens on the alfresco repository)

any ideas?

Tom

[mackoftrack]

I'm trying to do the same thing with no success...
Does anybody have this working with ZCS 6.0.x?

[mackoftrack]

wouldn't it be great if the developer of this zimlet actually responded to users?

[yqu]

Yes. zmprov mc default zimbraProxyAllowedDomains "*" is required for cross domain stuff.

[yqu]

Originally Posted by nowrap

hello,
i am running alfresco with https and can get the zimlet to work with this scenario.

I added a redirect from http to https. but this also don't work. i am getting a 404 error from service/proxy. Within the target parameter the alfresco url is still http but now with port 443 added.

Is there any chance to run the zimlet with https?

regards
.nowrap


// edit
I opend the zip-file, replaced within the org_alfresco_zimbra.js all http:// with https:// and restartet zimbra.
Now it's working.

Yeah. We need to move it as a configuration of the zimlet

[yqu]

Originally Posted by christian.kieft

is there any workaround for storing the user password plaintext in the ldap?

some admins need to be able to do "zmprov ga <acc>" but they should not be able to see the user password.

I understand that the Zimlet needs to authenticate against Alfresco. But an option would be nice that the password is not stored (probably only in a js var, so that you enter it once upon login).

But anyway - it is a nice Zimlet!

Right now the zimlet will take the alfresco username/password as part of the zimlet configuration. That pair will be used to authenticate against alfresco aka getting a ticket and use it for all following calls. If the ticket expires, it will try to reconnect and create a new ticket.

[yqu]

Originally Posted by Paolo

I've also noticed that when I receive an email with either a pdf or a rtf file as attachment Zimbra doesn't display the option "Save to alfresco". No problems, for example, with odt or doc.
Is this a bug or a missing feature?

Paolo

I remember it should work for PDF file. For odt file, can you check the additional mimetypes that are defined in AlfMimeTypes.js. If it is not there, you can add it and give it another try.