topic Re: Alfresco WebDav SSL in Alfresco Archive

Alfresco WebDav SSL

ioudas — Wed, 24 Dec 2014 15:00:33 GMT

All,I have setup a webdav mapped drive for our windows 7 machines. Initially i had set up this using a standard http connection, and this works great. Except. whenever an app such as adobe reader or excel/office needs to open the file via explorer. It will not open the file or just prompt. In office

Re: Alfresco WebDav SSL

resplin — Mon, 05 Jan 2015 19:09:00 GMT

This sounds like a problem I documented in the WebDAV section of this blog post:

https://richard.esplins.org/siwi/2014/02/28/alfresco-and-windows/

<blockquote>
In order to have Windows connect to a secure WebDAV share, you will need a valid certificate. The one included in Alfresco is self signed. You can use a self signed certificate by installing it into the Certificate store of each client computer. I found that I had to install the certificate into the Trusted Root Certificate Authorities store. The Personal and Intermediate Certificate Authority stores appear to be ignored when mounting a drive. Also, Windows 7 does not give a certificate error–it just asks repeatedly for the username and password and fails silently.
</blockquote>

Good luck.

Re: Alfresco WebDav SSL

ioudas — Mon, 05 Jan 2015 19:24:40 GMT

Hah,

I actually followed this exact guide. Great to put a name on the face finally. I have followed this exact guide.

So i pushed out a SSL gpo, and setup the webdav to work with this webdav ssl cert. This allowed people to actually open the documents. Instead they would just stall or never open.

However even with a local cname or any ssl cert. Office/Adobe Reader/Excel still continually prompts when opening a file.

The use case is a replacement for google docs. I have implemented this.
However they want a backend, that can have the files edited from our office. the server has to be remote due to our network.
the front end uses the ftp interface for the mobile app our salespeople use… and i had to up the port ranges, but the front end works great.
its just the backend webdav/cifs users have a really hard time editing these files with office.