Client certificates (mutual tls) for webdav mounts #289
Replies: 7 comments 1 reply
-
Thanks for the suggestion, we have added it to the internal to-do list |
Beta Was this translation helpful? Give feedback.
-
Any news on this one? Thanks |
Beta Was this translation helpful? Give feedback.
-
I think this will maybe be done in-between our bigger tasks. Usually a few months until there is a time slot somewhere where we can push it in. There are a lot of things to do currently... But if you want to speed it up, feel free to contribute to the project. Ideally the contribution should be done in Jetpack Compose, as we will need to refactor DAVx5 to this in the future anyway. |
Beta Was this translation helpful? Give feedback.
-
Internal reference: bitfireAT/davx5#225 |
Beta Was this translation helpful? Give feedback.
-
Is this still alive? |
Beta Was this translation helpful? Give feedback.
-
Linked to #61 I can see mTLS be an alternative to headers. |
Beta Was this translation helpful? Give feedback.
-
Thanks for implementing this. |
Beta Was this translation helpful? Give feedback.
-
I have configured my webdav server behind reverse proxy with mutual tls so that it awaits for a client certificate before it responds to clients.
DAVx5 already support client certificates for advanced logins (special use cases)
mutual tls with client certificate authentication is an extra layer of security and it would be great if there was an option to also take advantage of it for webdav mounts
Beta Was this translation helpful? Give feedback.
All reactions