Bug 283329 - No WedDAV support with x509 certificate authentication
Summary: No WedDAV support with x509 certificate authentication
Status: REPORTED
Alias: None
Product: knetattach
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-04 17:29 UTC by Paul Millar
Modified: 2017-03-20 09:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Millar 2011-10-04 17:29:06 UTC
Version:           unspecified (using KDE 4.6.5) 
OS:                Linux

I have a WebDAV server that authenticates users by client X509 certificates.  This means that, to use the service, the client must provide an X509 certificate when establishing the secure context with the server.

Currently knetattach provides no option to specify which certificate is used when establishing the secure context.

Reproducible: Always

Steps to Reproduce:
Start dolphin
Select "Network" in "Places" side-bar.
Select "Add Network Folder" icon.
Select "WebFolder (webdav)" and select "Next >" button.
Complete "Name", "Server", "Port" and "Folder" fields.  Leave "User" field empty.  Select "Use encryption" option and select "Finish" button.


Actual Results:  
Connection fails with error message "Unable to connect to server.  Please check your settings and try again."


Expected Results:  
I expect to see some UI feature (dialogue- or text-box) that allows me to specify which certificate to use. (see KMail's support for S/MIME as a possible example).

After selecting an authorised user certificate, the connection should succeed.
Comment 1 Graham Perrin 2017-03-19 03:50:41 UTC
Is 'KDE and KIO webdav have no support for SSL client certificates' <https://bugs.kde.org/show_bug.cgi?id=365288> (2016-07-09) a duplicate of this bug?
Comment 2 Paul Millar 2017-03-20 09:54:41 UTC
Yes, Graham, I believe the problem bjoernv reported suffers from the same underlying problem: a lack of support for X.509 client certificate based authentication.

If it helps, I can provide access to a demo site and client-side X.509 credentials to help KDE developers, if that would help.

Cheers,

Paul.