Repository navigation
feat(elastic): configurable TLS options for Elasticsearch/OpenSearch - #11124
Open
MichaelUray wants to merge 1 commit into
Open
MichaelUray wants to merge 1 commit into
MichaelUray wants to merge 1 commit into
Conversation
The Elasticsearch client was created with only the node URL, so TLS connections to clusters whose certificate is signed by a CA outside the system trust store (self-signed or cluster-internal CAs) failed, with no way to configure trust. Add getElasticTlsOptions(), which builds the client ssl options from the environment: - ELASTIC_TLS_CA_FILE: PEM CA certificate (bundle) used to verify the server certificate. - ELASTIC_TLS_VERIFY=false: explicit opt-in to skip certificate verification; logs a warning. createElasticAdapter passes the options only when one of the variables is set, so the default behaviour is unchanged. The variables are documented in the fulltext service README. Fixes hcengineering#9974 Signed-off-by: Michael Uray <michaeluray@users.noreply.github.com>
MichaelUray
force-pushed
the
feat/elastic-tls-options
branch
from
October 26, 2026 13:28
79a5759 to
1b635b8
Compare
This branch has not been deployed
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
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.
Fixes #9974
Problem and change
The Elasticsearch client was created with only the node URL, so TLS connections to clusters whose certificate is signed by a CA outside the system trust store (self-signed or cluster-internal CAs) failed, with no way to configure trust.
Add getElasticTlsOptions(), which builds the client ssl options from the environment:
createElasticAdapter passes the options only when one of the variables is set, so the default behaviour is unchanged. The variables are documented in the fulltext service README.
Tests
New unit tests
foundations/server/packages/elastic/src/__tests__/tls.test.ts. The default (no variables set) is unchanged.