EPMDEDP-17262: fix: Verify TLS certificates in integration secret connection checks - #311
Merged
Conversation
Collaborator
Pipeline
|
| Status | Task | Duration |
|---|---|---|
| ✅ | github-set-pending-status | 6s |
| ✅ | fetch-repository | 13s |
| ✅ | init-values | 6s |
| ✅ | get-cache | 2m9s |
| ✅ | commit-validate | 6s |
| ✅ | dockerfile-lint | 7s |
| ✅ | helm-lint | 6s |
| ✅ | helm-docs | 9s |
| ✅ | build | 47s |
| ✅ | sonar | 19s |
| ✅ | save-cache | 8s |
| ✅ | buildkit-build | 18s |
| ✅ | github-report-pipeline-status | 6s |
…nection checks Connection checks accepted any certificate while re-sending live integration credentials on every heartbeat, letting a network-position attacker harvest them and a MITM'd endpoint show a green status. Verify against the system trust store. For self-signed or private-CA endpoints the chart mounts CAs from an existing secret via caCerts, listed in SSL_CERT_DIR next to the system bundle. An untrusted certificate only marks the secret disconnected with the x509 error; nothing else is blocked. BREAKING CHANGE: integrations with untrusted certificates report connected=false until their CA is mounted through caCerts. Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Connection checks accepted any certificate while re-sending live integration credentials on every heartbeat, letting a network-position attacker harvest them and a MITM'd endpoint show a green status.
Verify against the system trust store. For self-signed or private-CA endpoints the chart mounts CAs from an existing secret via caCerts, listed in SSL_CERT_DIR next to the system bundle. An untrusted certificate only marks the secret disconnected with the x509 error; nothing else is blocked.
BREAKING CHANGE: integrations with untrusted certificates report connected=false until their CA is mounted through caCerts.