fix: use ca_cert instead of ca_cert_file #1164
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Credhub ca_cert_file was not being generated during installation. Instead, the Ops Manager certificate was being included in an unexpected configuration key. Previously, the broker app ran on Diego and utilized the Cloud Foundry certificate trust store (the Ops Manager CA certificate was located in the container’s /etc/cf-system-certificates path). Now, the broker runs on its own VM without automatic injection of the Ops Manager root CA or CF trust store. Although ca_cert was present in the job configuration, the broker wasn’t utilizing it, leading to the following error: `tls: failed to verify certificate: x509: certificate signed by unknown authority.`
zucchinidev
force-pushed
the
known_issue_credhub_cert
branch
from
ae31754 to
a7546cd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Credhub
ca_cert_filewas not being generated during installation. Instead, the Ops Manager certificate was being included in an unexpected configuration key.Previously, the broker app ran on Diego and utilized the Cloud Foundry certificate trust store (the Ops Manager CA certificate was located in the container’s /etc/cf-system-certificates path).
Now, the broker runs on its own VM without automatic injection of the Ops Manager root CA or CF trust store. Although ca_cert was present in the job configuration, the broker wasn’t utilizing it, leading to the following error:
tls: failed to verify certificate: x509: certificate signed by unknown authority.Checklist: