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

Mutual tls / client certificate authentication #243

Open
3 tasks done
ippocratis opened this issue Mar 12, 2023 · 1 comment
Open
3 tasks done

Mutual tls / client certificate authentication #243

ippocratis opened this issue Mar 12, 2023 · 1 comment

Comments

@ippocratis
Copy link

ippocratis commented Mar 12, 2023


If this is your first feature request, read our contribution guidelines.


Pre-Submission checklist

  • There is no existing issue that already asks for this feature.
  • The feature already exists in rclone (on your PC or in Termux)
  • I am prepared to help make this feature

What version of RCX are you using (About -> App version)?

1.12.2

What problem are you trying to solve?

I have my webdav server configured with mutual tls and it awaits for a client certificate. I have installed the p12 cert on my android device and it can be picked from browsers and compatible apps like e.g. davx5

What should RCX be able to do differently to help with this problem?

Talk with the android keystore and pickup client certificates when it is required

@ippocratis ippocratis changed the title Mutual tls / cliemt certificate authentication Mutual tls / client certificate authentication Mar 12, 2023
@ippocratis
Copy link
Author

More on this

I tried to import a config

Rclone documentation link for webdav mounts States that:

If you want you can serve over https. You will need to supply the --cert and --key flags. If you wish to do client side certificate validation then you will need to supply --client-ca also. --cert should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. --key should be the PEM encoded private key and --client-ca should be the PEM encoded client certificate authority certificate.

My config looks like

[webdav]
type = webdav
url = https://my.webdav.url
vendor = other
user = username
pass = password
client-ca = /path/to/cert_name-CA.crt
client-cert = /path/to/cert_name.crt
client-key = /path/to/cert_name.key

The config imports OK but the webdav does not mount

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

1 participant