Mutual TLS authentication #702
Conversation
|
If I got it correctly, for valid client-side certificate authentication you need a client certificate and its matching private key. They can be both in one file or in two separate files. I would suggest adding this to the documentation of the new parameter like requests does it, that it is also possible to have a tuple with both file paths instead of one path only. From the requests documentation
|
|
Sorry, been consumed lately but will get this reviewed this week! |
|
I've updated the documentation to more explicitly state the supported values. I considered explicitly linking to the Requests documentation - but I'm not sure whether this would be preferred, especially as links can break over time. |
|
Hello! Are there any updates on this PR? |
|
@aviau I think this PR can be merged. |
|
Sure, LGTM. |
A recreation of #677 because I accidentally made a mess of my branch :(
With the Python requests module, it is possible to configure a client certificate to use for mutual TLS authentication, for example if an nginx instance in front of influxdb is performing the TLS termination and has a whitelist of allowed CNs.
This PR adds a new optional argument to the client constructor which passes through the path to such a client certificate to the requests session.