feat: Added Params for CA Certs in MSSQL Config #698
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.
When establishing an SSL connection to MSSQL currently, bb8 times out due to a mismatch in CA certificates since underlying default behavior from tiberius is to validate server certificate against system-truststore.
This change enables 2 new parameters in the connection string for MSSQL to address custom CA certificate use cases (description extracted from tiberius config documentation):
This will resolve issue #509 and is a requested feature at the end of the thread.