-
Notifications
You must be signed in to change notification settings - Fork 63
Self signed / Let's Encrypt SSL certificate support #90
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
Hello Emmanuel, to be honest, I have no real experiences with SSL certificates. If I understand xmlrpclib pydoc right,
must support as additional optional args the xmlrpclib context parameter. But I have currently no idea, what you have to define as ssl.SSLContext. So the TestlinkAPIGenric.py code change would be something like
and your test call might be
Helps this a little bit ? Would it be possible for you to play around with this changes and check, if you can find a working ssl.context definition? Regards Luiko |
From what i've seen (e.g : https://stackoverflow.com/questions/30461969/disable-default-certificate-verification-in-python-2-7-9) the idea is to create a |
Not sure how to test properly in a python project but here is what works for me. Did the following edit in testlinkapigeneric.py then setup.py install and now my api calls work with self signed certificate
Trouble is ssl does not have the _create_unverified_context() before 2.7.9 and it seems xmlrpclib does not support a context either. Solution would be to use transport with something like
But transport is already used I presume. Do you know how ? |
Hello Emmanuel, using transport was introduced with #36 (and adjusted with #56) to support proxy configurations. It is set in TestLinkHelper.connect() - getProxiedTransport(). Did I understand you right, that you are using a Python Version before 2.7.9 ? Regards Luiko |
No no I'm using 2.7.13. My point was that in order to make a patch that is compatible with most versions of Python Transport should be used instead of ssl context. |
Hello Emmanuel, TestLinkHelper should know define the uncertificate context, when you call it with a HTTPS url without defining a special sssl context. Hope this works and help, regards Luiko |
seams to work, if not please reopen. |
Hi,
I'm trying to use your plugin with a testlink instance deployed with a let's encrypt ssl certificate. When I try a simple API call through your plugin I get a "certificate verify failed" error caused, I presume, by xmlrpclib. Any idea what would be the best way to support self-signed certificates ?
Thanx in advance
The text was updated successfully, but these errors were encountered: