Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ownCloud Desktop client 2.5.1 for MacOS: unable to configure client-side certificates #6940

Closed
eta-orionis opened this issue Dec 23, 2018 · 2 comments

Comments

@eta-orionis
Copy link

eta-orionis commented Dec 23, 2018

Expected behaviour

Client side certificates are configured and used to connect to the server

Actual behaviour

I can choose client-side certificates in the configuration dialog, but they do not get used; The server rejects the connection with a 400 error, "no SSL certificates sent", and the configuration dialog says "Could not load certificate", similar to the issue in #6128

The difference to that issue is that i am typing the password correctly (verified multiple times). Also the certificate works and is not expired.
image

Steps to reproduce

  1. install oc desktop client 2.5.1 (clean install, not update from previous client! see below "Workaround")
  2. Configure a new account
  3. Input server URL. When server rejects connection without client certificates, choose to configure client side certificates
  4. choose certificate, enter password
  5. Click OK. Server will reject with code 400, "no SSL certificates sent", and configuration dialog will say "Could not load certificate"

Server configuration

Operating system: Debian Jessie
Web server: Nginx
Database: MariaDB
PHP version: 5.6
ownCloud version: 10.0.10.4

Client configuration

Client version: 2.5.1
Operating system: macOS High Sierra 10.13.6
OS language: en-US
Installation path of client: /Applications

Logs

Client Log: https://gist.github.com/eelmasllari/e901fd6605779705ae10eab53807e4de

Partial Workaround

  1. Install desktop client v 2.3.3
  2. Configure the connection there
  3. Update to desktop client v2.5.1
    Now everything works, except that you cannot add new accounts to the 2.5.1 installation; the same problem will appear and only the accounts that were configured with 2.3.3 will continue working
@michaelstingl
Copy link
Contributor

Related to #6911 ? If this is the same issue, we could close this duplicate and provide missing information in #6911

@ogoffart
Copy link
Contributor

closing as duplicate of #6911

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants