Fix ssl context when certificate is provided #235
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have a tool that (reliably) uploads test results to our RP instance.
We recently added https certifacates to our servers.
But trying to use
verify_ssl='C:/GIT/MyProject/myCert.crt'
with the ASYNC_THREAD client resulted in the following error:I tracked down the issue to
reportportal_client\aio\client.py
where we create the ssl context withssl.create_default_context(ssl.Purpose.CLIENT_AUTH, cafile=self.verify_ssl)
Using the
purpose=ssl.Purpose.CLIENT_AUTH
seems to be the wrong and a quite common mistake.According to this post on stackoverflow and the documentation of ssl library we must:
As we are a client connecting to the RP-Servers, we have to use
purpose=ssl.Purpose.SERVER_AUTH
(we as a client want to authenticate the server with the certificate)