-
-
Notifications
You must be signed in to change notification settings - Fork 854
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
Client certificate not being passed #558
Comments
Hey @el-pablo I believe you may just be having an issue with syntax.
|
Thanks for the response @hdost - I just tried that and it doesn't seem to have helped.... |
What error does it seem to be giving you? |
I get the following, which I believe is because it is not sending a certificate.
|
This may be something we need to fix https://stackoverflow.com/a/18579484/1966876 |
I went down that little rabbit hole, but in the end adding the line:
in the client.py init function seems to fix it just fine... |
I can send a pull request if it helps? |
PRs are always welcome :)
…________________________________________
*Harold Dost* | @hdost
On Tue, May 8, 2018 at 11:26 AM, Paul Thomas ***@***.***> wrote:
I can send a pull request if it helps?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#558 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAnTBuj3k0qw5UhrPbjlEmGcDcvJSISqks5twbkmgaJpZM4TqXWe>
.
|
The certificate was not being passed through to ResilientSession. This change makes sure that it's always passed through, no matter which options are given. If the client_cert option is not given, then it will be set to None, which is the same effect as it not being passed.
would this also fix: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You way want to consider using the Sponsor button in order to persuade someone to address it. |
My company is using mutual certificate authentication for our Jira instance. There's an option in the API to specify a client_cert parameter, but when I use it is ignored.
This is how I'm doing it:
Which gives me an SSL handshake error.
I've tried adding this at line 453 of client.py:
self._session.cert = self._options['client_cert']
and it fixes the issue, but I'm a complete novice with Python and wondered whether this is just a hack and that there is something that I'm doing wrong.
If I've genuinely found a bug I'm happy to raise a pull request, but given my complete amateur status I thought I'd ask here first!
Thanks
The text was updated successfully, but these errors were encountered: