Skip to content
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

Certificate verify failed #36

Closed
HeathNaylor opened this issue Jan 26, 2016 · 3 comments
Closed

Certificate verify failed #36

HeathNaylor opened this issue Jan 26, 2016 · 3 comments

Comments

@HeathNaylor
Copy link

I have a certificate for a domain but am referencing a local vault server over TLS in my script. I want to ignore the tls verification problem but I get the following error when I do assert client.is_authenticated()

SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
@ianunruh
Copy link
Member

How are you creating the client? Did you try the verify=False flag?

@ianunruh ianunruh added the waiting-reply waiting for more information (probably for a while) label Jan 27, 2016
@HeathNaylor
Copy link
Author

That is better but throws this:

/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:120: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning

I can get around this by importing logging and disabling warning capture.

import logging
logging.captureWarnings(True)

I would not consider this a long term solution. To truly fix this would I need to create my own CA and install the root cert on the system with hvac?

@ianunruh
Copy link
Member

You can either install the CA certificate on the system or you can set the verify flag to the path of the CA certificate, depending on your use case.

@ianunruh ianunruh removed the waiting-reply waiting for more information (probably for a while) label Jan 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants