Release v2.0.0
Changed
- The client now derives the OAuth token endpoint from the same host and port as the gRPC connection instead of a hardcoded management port (
8080), matching the Chronicle Kernel's consolidation onto a single port (35000). - TLS is now required for every connection, including local development. The gRPC channel trusts the Kernel's auto-generated self-signed development certificate automatically, with no configuration needed.
- The default local-development connection string is now
chronicle://localhost:35000(TLS implicit) instead of appending?disableTls=true. ThedisableTlsoption is still supported for callers connecting through something that terminates TLS for them (e.g. a plaintext-terminating proxy).
Removed
- Removed the
-p 8080:8080port mapping from the root README's docker run command and the console sample'sdocker-compose.yml— the management port no longer exists on the Kernel.
Summary
This is a breaking change: clients built against the previous two-port Kernel (gRPC on 35000, OAuth/management on 8080, TLS optional) will not connect to a Kernel that has consolidated onto the single-port model, since cleartext HTTP/2 can no longer share a port with HTTP/1.1.