added custom CA support in dispatcher and server for secure TLS connections #2266
+334
−121
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.
Support for Custom CA Certificates in Dispatcher
Overview
This feature is particularly useful for customers who need to interact with internal services behind a VPN or private infrastructure using self-signed certificates.
Configuration
Users can specify a custom CA certificate in the Dispatcher configuration using either a file path or a direct certificate string.
Dispatcher Configuration Fields
CACertPath
: Path to the CA certificate file (PEM format). This certificate will be added to the trusted root CA pool.CACertString
: PEM-encoded CA certificate string. If provided, this will be used instead of reading from a file.Example JSON Configuration
Example Environment Variable Configuration
If both CACertPath and CACertString are provided, CACertString takes precedence.