Repository navigation
Release v19.141.0
Summary
TLS certificate validation settings in the Chronicle .NET client are now tracked as explicit choices. The default when the setting is omitted does not change in this release.
Changed
- The client now distinguishes an explicitly configured TLS validation setting from an omitted one, and keeps that choice through connection string parsing, building and credential helpers.
- An explicit setting to validate certificates always takes precedence over a setting to skip validation.
- A warning is logged at startup when certificate validation is skipped, and it is not logged when TLS is disabled.
- Documentation covers configuring validation explicitly, development certificate behaviour, and the planned change of the default in the next major release.