You are viewing limited content. For full access, please sign in.

Question

Question

WebDav Configuration

Version 11
Updated February 28, 2023
asked on July 4, 2021

Dear All,

We upgraded laserfiche to version 11. We would like to configure WebDav in the following environment and I did not get any information in the online help file.

 

Windows Server 2019

Port 80 not allowed 

http not allowed 

 

1. instead of port 80 any other port supported ? If yes, which port?

2. instead of http we need to configure with https so we need more configuration information.

3. Step by Step configuration details for Windows Server 2019.

 

Thank You.

 

 

0 0

Replies

replied on July 6, 2021

The documentation only talks about port 80 and http, but it would be worth trying it with https. Most of the web has moved to fully supporting - or even requiring - https, but that might not include webdav. There wouldn't be a certificate configuration separate from the one already documented for LFS for all of its other clients. And the server OS doesn't really come into it, but keep in mind that the client OS is the one that needs to bring its own webdav implementation, and I don't know the state of that on modern OSes.

1 0
replied on February 28, 2023

We currently have this working with http, but we were unable to map with https. We do have an appropriate certificate in place. Has anyone got this to successfully work with https before? If so, was there any special configuration needed to get it working?

0 0
replied on February 28, 2023

I haven't set it up myself, but if you already have http working, there are only a few things that can go wrong when moving to https. I would assume that the webdav client can use https, because it would just be relying on a library for its networking code. So if there isn't anything blocking network traffic to port 443, the problem would be in the certificate exchange or setting up the secure channel. For the certificate, it needs to match the hostname that the webdav client is using, and it needs to be trusted by the client. The other thing that can go wrong is that a lot of organizations have dropped support for TLS versions before 1.2. It's definitely possible that the webdav client is old enough that it only supports TLS versions before 1.2.

Wireshark is a good tool for figuring out where this is going wrong.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...