Make DB Direct certificates server_ca configurable #15650
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.
So far, in development, the server_ca certificate has been fetch from the CA used to sign client certificates, but in production we need to control what should be in it or if it should be disabled (e.g. for server certificates signed by CA for which all systems include their root certificates).
So I've added a new configuration parameter
dbdirect.certificates.server_ca
to control this.client_ca
value (for convenience of chef-controlled configurations)disabled
prevents inclusion of server_ca with client certificates and omits also references to it in the README.