Commander One is a reliable Mac OS X WebDAV client with an intuitive dual panel interface and lots of handy features for the best connection experience with remote servers. Move, edit or delete your online files on the server, copy files from one WebDAV server to another in a couple of clicks.
Remove Webdav Module
Hi,
I've set up an Apache2 WebDAV & Web server which is only accessible by https and for clients authenticating themselfes by a suitable client certificate. My question is regarding the WebDAV client of the Mac I use to accesss the WebDAV server: When I try `Go To' -> `Connect to Server'in the Finder, the connection gets refused with error -50. In the console log I see:
09.05.08 13:03:15 webdavfs_agent[21544] (result 0 ) failed with 1; No such file or directory; file: /SourceCache/webdavfs/webdavfs-252/mount.tproj/webdav_agent.c; line: 314
I've installed the client certificate into the keychain (including the CA certificate I used for self-signing the client certificate), but to my impression, it looks as if the Finder (or, to be more exact, the webdavfs agent/mountwebdav process) does not care for sending the client certificate when the WebDAV server requests this, and therefore the server terminates the connection. I've also set up a certificate association for the server and client certificate into the key chain, but this shows also no result.
Importing the client certificate into Firefox works perfect, I can access the Web pages on the same server without problems (Web page access is also protected by the same client certificate), so obviously Firefox shows the right certificate when accessing the server. And, BTW, WebDAV access with client certificates works also from Windows XP's File Explorer ...
My questions:
Does the Mac OS X 10.5.2 WebDAV client support client authentification by client certificates?
(If not, why not?)-:
If yes, are there possibilities to debug the (failed) connection in more depth, i.e. to find out if the WebDAV client sends a client certificate to the WebDAV server?
Are there 3rd party WebDAV clients for Mac OS X 10.5.2, which are able to do authentication by a client certificate?
(I tried to compile davfs2 on Darwin, but the OS interface used by davfs2 differs considerably from Darwin).
Viele Grüße,
Heiko
I've set up an Apache2 WebDAV & Web server which is only accessible by https and for clients authenticating themselfes by a suitable client certificate. My question is regarding the WebDAV client of the Mac I use to accesss the WebDAV server: When I try `Go To' -> `Connect to Server'in the Finder, the connection gets refused with error -50. In the console log I see:
09.05.08 13:03:15 webdavfs_agent[21544] (result 0 ) failed with 1; No such file or directory; file: /SourceCache/webdavfs/webdavfs-252/mount.tproj/webdav_agent.c; line: 314
I've installed the client certificate into the keychain (including the CA certificate I used for self-signing the client certificate), but to my impression, it looks as if the Finder (or, to be more exact, the webdavfs agent/mountwebdav process) does not care for sending the client certificate when the WebDAV server requests this, and therefore the server terminates the connection. I've also set up a certificate association for the server and client certificate into the key chain, but this shows also no result.
Importing the client certificate into Firefox works perfect, I can access the Web pages on the same server without problems (Web page access is also protected by the same client certificate), so obviously Firefox shows the right certificate when accessing the server. And, BTW, WebDAV access with client certificates works also from Windows XP's File Explorer ...
My questions:
Does the Mac OS X 10.5.2 WebDAV client support client authentification by client certificates?
(If not, why not?)-:
If yes, are there possibilities to debug the (failed) connection in more depth, i.e. to find out if the WebDAV client sends a client certificate to the WebDAV server?
Are there 3rd party WebDAV clients for Mac OS X 10.5.2, which are able to do authentication by a client certificate?
(I tried to compile davfs2 on Darwin, but the OS interface used by davfs2 differs considerably from Darwin).
Viele Grüße,
Heiko
MacBook Pro, Mac OS X (10.5.2), OpenSSL 0.9.7m 23 Feb 2007
Posted on
WebDAV allows users to access Confluence content via a WebDAV client, such as 'My Network Places' in Microsoft Windows. Provided that the user has permission, they will be able to read and write to spaces, pages and attachments in Confluence. Users will be asked to log in and the standard Confluence content access permissions will apply to the equivalent content available through the WebDAV client.
Mapping a Confluence WebDAV network drive requires a set of specific criteria to be met. For specific information, please see Windows Network Drive Requirements.
Introduction to Confluence's WebDAV Client Integration
By default, all WebDAV clients have permission to write to Confluence. Write permissions include the ability for a WebDAV client to create, edit, move or delete content associated with spaces, pages and attachments in a Confluence installation.
On this page:
Related pages:
On the 'WebDAV Configuration' screen in the Confluence Administration Console, you can:
![Windows Windows](/uploads/1/2/6/4/126443979/714890262.png)
- Deny a WebDAV client write permissions to a Confluence installation using a regular expression (regex)
Note:
- The 'WebDav Configuration' page is only available if the WebDAV plugin has been enabled. This plugin is bundled with Confluence, and can be enabled or disabled by the System Administrator.
- The settings on the 'WebDav Configuration' page do not apply to external attachment storage configuration.
Using a WebDAV Client to Work with Pages
The following sections tell you how to set up a WebDAV client natively for a range of different operating systems. WebDAV clients typically appear as drives in your operating system's file browser application, such as Windows Explorer in Microsoft Windows, or Konqueror in Linux.
Accessing Confluence in Finder on Mac OSX
You can successfully connect but you can't see content when using HTTPS, so this technique won't work for Confluence Cloud. Use a third-party WebDAV client instead.
To use Finder to view and manage Confluence content:
- In Finder choose Go > Connect to Server
- Enter your Confluence URL in this format:For example if your Confluence URL is http://ourconfluence.sample.com/wiki you would enter:
- Enter your Confluence username and password and click ConnectUse your username (jsmith), not your email address, unless your email address is your username.
Confluence will appear as a shared drive in Finder. You can use the same URL to connect using a third party WebDav client, like CyberDuck.
Accessing Confluence in Explorer in Microsoft Windows
![Webdav Client For Mac Webdav Client For Mac](/uploads/1/2/6/4/126443979/481891919.jpg)
This section covers the two methods for configuring a WebDAV client natively in Microsoft Windows:
- As a network drive
- As a web folder
If possible, use the network drive method as this will enable more comprehensive WebDAV client interaction with Confluence than that provided by a web folder. However, your Confluence instance must meet several environmental constraints if you use this method. If you cannot configure your instance to meet these requirements, then use the web folder method or third-party WebDAV client software.
If you're using SSL you may need to add
@SSL
to the end of your server URL, for example:If you run into any problems with the procedures in this section, please refer to the WebDAV Troubleshooting page.
Windows Network Drive
To map a Confluence WebDAV client network drive, your Confluence instance must be configured so that all of the following criteria is met:
- Has no context root
- There's an issue that can prevent Network Drives from being mapped. Please use the Network Folders steps below as a workaround.
The reason for these restrictions results from limitations in Microsoft's Mini-Redirector component. For more information, please refer to Microsoft's server discovery issue.
To map a Confluence WebDAV client network drive in Microsoft Windows:
- In Windows go to Map Network Drive.
See Map a network drive in the Windows documentation to find out how to get to this in your version of Windows. - Specify the following input to map the WebDAV client as a network drive:
- Drive:
<Any drive letter>
(for example,Z:
) - Folder:
<hostname>webdav
(for example,localhostwebdav
)
- Drive:
- Click Finish
When prompted for login credentials, specify your Confluence username and password.
Windows Web Folder
To map a Confluence WebDAV client web folder:
- Go to My Network Places and choose Add a network place and follow the prompts.
- In the 'Internet or network address' field, enter the URL for the Confluence WebDAV location (for example,
http://<confluence server url>/confluence/plugins/servlet/confluence/default
orhttp://<confluence server url>/plugins/servlet/confluence/default
) and click Next - Enter your Confluence username and password
- Provide a meaningful name for your web folder and proceed with the wizard
- Click Finish
Screenshot: A Confluence WebDAV Client Web Folder in Windows XP
Setting up a WebDAV client in Linux
There are many tools and mechanisms available for configuring WebDAV clients in these operating systems. Therefore, we have chosen to demonstrate this using the file manager Konqueror, which is part of the Linux K Desktop Environment.
To set up a Confluence WebDAV client in Konqueror:
- Open Konqueror
- In the 'Location' field, enter the URL for the Confluence WebDAV location using the 'protocol'
webdavs
(for example,webdavs://<confluence server url>/confluence/plugins/servlet/confluence/default
orwebdavs://<confluence server url>/plugins/servlet/confluence/default
) and pressEnter
. - Enter your Confluence username and password if prompted
You should be able to click to load many, but not all files. In practice, you would normally save a modified file locally, then drag it to the Konqueror window to upload it to Confluence.
Restricting WebDAV Client Write Access to Confluence
In earlier versions of the WebDAV plugin, separate options for restricting a WebDAV client's write permissions (that is, create/move, edit and delete actions), were available. However, in the current version of this plugin, they have been simplified and combined into a general write permission restriction that covers all of these actions.
WebDAV clients are now denied write permission to your Confluence installation by setting a regex that matches specific content within the WebDAV client's user agent header. Upon setting a regex, it will be added to a list of restricted WebDAV clients. Any WebDAV clients whose user agent header matches a regex in this list will be denied write permission to your Confluence installation.
Example: A PROPFIND method header generated by a Microsoft Web Folder WebDAV client, showing the user agent header field:
Unlike earlier versions of the WebDAV plugin, which could only restrict write permissions for all WebDAV clients, the current version of this plugin allows you to restrict write permissions to specific WebDAV clients.
To restrict a WebDAV client's write access permissions to your Confluence installation:
- Choose the cog icon , then choose General Configuration
- Choose 'WebDav Configuration' in the left panel
- Enter a regex that matches a specific component of the user agent header sent by the WebDAV client you want to restrict.
- Click the 'Add new regex' button
Repeat steps 3 and 4 to add a regex for each additional WebDAV client you want to restrict. - Hit Save
To restore one or more restricted WebDAV client's write access permissions to your Confluence installation:
- Choose the cog icon , then choose General Configuration
- Click WebDav Configuration under 'Configuration' in the left panel
- Select the regex(es) from the list that match(es) the user agent header sent by the restricted WebDAV client(s) you want to restore
- Click the Remove selected regexes button
- Hit Save
Screenshot: WebDAV configuration
Disabling Strict Path Checking
If you observe any idiosyncrasies with your WebDAV client, such as a folder that does exist on your Confluence site but is missing from the client, you can disable the WebDAV plugin's strict path checking option, which may minimize these problems.
To disable the WebDAV plugin's strict path checking option:
- Choose the cog icon , then choose General Configuration
- Click WebDav Configuration under 'Configuration' in the left panel
- Clear the 'Disable strict path check' check box
- Hit Save
Virtual Files and Folders
In the unlikely event that you have problems with the WebDAV client's performance or stability, you can enable access to automatically generated (that is, virtual) files and folders.
Note:
By default, these options are hidden on the 'WebDAV Configuration' page. To make them visible, append the parameter
?hiddenOptionsEnabled=true
to the end of your URL and reload the page. For example:Screenshot: The Hidden Virtual Files and Folders Option
To enable or disable access to virtual files and folders:
Webdav Client Mac Os X Download
- Choose the cog icon , then choose General Configuration
- Click WebDav Configuration under 'Configuration' in the left panel
- Amend your URL as described in the note above and reload the 'WebDav Configuration' page
- Select or clear the check box options in the 'Virtual Files and Folders' section as required
- Hit Save
Last modified on Oct 2, 2018
Was this helpful?
YesProvide feedback about this article Powered by Confluence and Scroll Viewport.