Repository navigation
Release v19.113.0
The .NET client could not reach a kernel running with tls.enabled=false: disableTls was not a .NET connection-string option, so every channel dialed https://, and the token request failed with "The SSL connection could not be established". The issue suggested switching the token endpoint to http://, but that cannot work: the kernel never serves /connect/token without TLS (KernelListeners requires an external HTTPS authority when TLS is off and authentication is on). So instead of an http:// token request that would 404, the client now refuses that combination up front with a clear error. (part of #5443)
Added
disableTls=truein the .NET connection string (ChronicleConnectionString.DisableTls,ChronicleConnectionStringBuilder.DisableTls). The gRPC channel and the least-connections probes connect over cleartext HTTP/2 (h2c).ClientCredentialsRequireTls, thrown when creating a connection that combines explicit client credentials withdisableTls=true. The message points toauth=noneandapiKey=.
Changed
- A
disableTls=trueconnection string without credentials no longer falls back to the development credentials. It connects without authentication.