-
Notifications
You must be signed in to change notification settings - Fork 112
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
Use OS certificate bundle #1617
Conversation
/cc @jrafanie could you take a peek to see if this works like you thought it should? |
LGTM once the comments are addressed. 👍 |
962346c
to
295bd48
Compare
push: fixed updates
|
We are getting away from storing configuration files in /root Now we are storing the ssl certificates in the standard linux location
295bd48
to
e98b3f9
Compare
Checked commit kbrock@e98b3f9 with ruby 2.6.3, rubocop 1.13.0, haml-lint 0.35.0, and yamllint |
Checked commit kbrock@e98b3f9 with ruby 2.6.3, rubocop 1.13.0, haml-lint 0.35.0, and yamllint |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - @bdunne Can you take another look?
Part of ManageIQ/manageiq-appliance#341
This gets database ssl keys out of
/root
, which is only accessible toroot
user, and into a standard location which is accessible to other users, namely usermanageiq
root.crt
in/root
so user manageiq can use itpostgres.key
in /var/vmdb/ sincepostgres
can not access those files.ssl_ca_file=root.crt
. We only use server side certificates and not client side certificates.