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

Update docs on SSL certificate location configuration #56

Open
ericjmcd opened this issue Oct 16, 2023 · 0 comments
Open

Update docs on SSL certificate location configuration #56

ericjmcd opened this issue Oct 16, 2023 · 0 comments

Comments

@ericjmcd
Copy link

Env: python3.8 on Ubuntu 20.04 running tcms_api 12.2

In testing with the default Kiwi Docker setup, I found that after I had installed the ca.crt (retrieved from static/ca.crt and copied to /etc/share/ca-certificates/ and installed with sudo dpkg-reconfigure ca-certificates), I had to:

  • Use url = https://buildkitsandbox/xml-rpc in my ~/.tcms.conf or a I would get an SSL error with hostname mismatch (I just hacked /etc/hosts to set buildkitsandbox to 127.0.0.1)
  • Set the env var SSL_CERT_FILE = /etc/ssl/certs/ca-certificates.crt or the SSL context deep inside the connection calls would not find any certs (context.get_ca_certs() returned an empty list)

Python requests uses the REQUESTS_CA_BUNDLE env variable which worked so I knew I had the correct cert but had a lot of trouble figuring this out. Adding something to the docs about this would be very helpful for others that are struggling with certificate verification.

Of course, I'm new to all this so if I missed something or there is an easier/cleaner way to do this, I'd love to know what that is.

atodorov added a commit that referenced this issue Jun 4, 2024
however this won't go into official documentation because it is not a
supported method of consuming Kiwi TCMS, users should always have valid
SSL certificates.

Closes #56
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

1 participant