-
Notifications
You must be signed in to change notification settings - Fork 670
Specify CA certificate #204
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
Comments
Definitely an interesting feature to implement. Thanks for the suggestion :) |
It looks like this has been implemented? When I set |
Finally getting around to looking into this. Yeah, it looks like under the hood this is already exactly what requests does and that we should be able to use it that way. Furthermore, this can be done safely as this behavior appears even in the earliest version of requests supported by python-gitlab. |
- Also updates documentation - See issues python-gitlab#204 and python-gitlab#270
- Also updates documentation - See issues python-gitlab#204 and python-gitlab#270
- Also updates documentation - See issues python-gitlab#204 and python-gitlab#270
- Also updates documentation - See issues python-gitlab#204 and python-gitlab#270
- Also updates documentation - See issues python-gitlab#204 and python-gitlab#270
- Also updates documentation - See issues python-gitlab#204 and python-gitlab#270
- Also updates documentation - See issues python-gitlab#204 and python-gitlab#270
Fixed by @mdhausman in #294. |
In
requests
, one can setverify
to the path of a CA certificate used to verify the the connection. This is really useful for CE instances when orgs run their own CA (ie, "self-signed"). This feature would allow me to not have to use ssl_verify=False.The text was updated successfully, but these errors were encountered: