Release 1.6.0

What's New

• Bug fixes and library updates
• Change to cluster add peer
• Experimental multi-underlay SDK support
• Experimental SDK flow-control support

Cluster Add Peer Change

The ziti agent cluster add command no longer supports the --id argument
for providing the peer id. The add operation will now always connect to the
peer, verify the certs and get the peer advertise address and id from the
peer directly. This will ensure that the peer is reachable and valid before
it is added to the cluster.

Multi-underlay SDK support

For SDKs which support it, the edge router now supports a separate control channel
connection along side the data connection. If the SDK doesn't request separate
channels, the edge router will continue to work with a single connection. This
feature is still experimental and may have bugs, may be changed or be removed.

SDK Flow-control

For SDKs which support it, the edge router now supports delegating flow control
to the SDK. This feature is still experimental and may have bugs, may be changed
or be removed.

Component Updates and Bug Fixes

• github.com/openziti/channel/v4: v3.0.39 -> v4.0.6

  • Issue #182 - MultiListener can deadlock
  • Issue #180 - Add GetUserData to Channel interface
  • Issue #176 - Multi-channel need a mechanism to notify the txer that the underlay has closed
  • Issue #172 - Support multi-underlay channels

• github.com/openziti/identity: v1.0.100 -> v1.0.101

  • Issue #64 - Support a way to check if a cert/serverCert can be saved

• github.com/openziti/metrics: v1.3.0 -> v1.4.1

  • Issue #53 - Add reporter useful for emitting metrics to stdout

• github.com/openziti/sdk-golang: v0.25.1 -> v1.1.0

  • Issue #702 - [Go SDK] Support xgress flow control from the SDK
  • Issue #722 - Move xgress impl to SDK
  • Issue #717 - ER connection race condition can leak connections
  • Issue #689 - Concurrent map iteration and modification in getEdgeRouterConn causes panic
  • Issue #701 - Support multi-underlay channels for edge router connections

• github.com/openziti/transport/v2: v2.0.167 -> v2.0.168

• github.com/openziti/xweb/v2: v2.3.0 -> v2.3.1

• github.com/openziti/ziti: v1.5.4 -> v1.6.0

  • Issue #3005 - Always check that a controller is reachable and valid before adding it to an HA controller cluster
  • Issue #2986 - [Router] Support xgress flow control from the SDK
  • Issue #2999 - OIDC JWT backed sessions cannot verify extended certs
  • Issue #2997 - Add Authenticator Id to OIDC JWTs/return for current-api-session
  • Issue #2904 - Support client certificate authorities in TLS handshake
  • Issue #2973 - CLI: add a subcommand to retrieve network JWT
  • Issue #2984 - Extend enrollments does not return a full chain
  • Issue #2930 - Support multi-underlay channels for the edge SDK
  • Issue #2978 - Create loop4 sim for testing circuit contention and scale
  • Issue #2981 - Remove PayloadBufferForwarder API from xgress retransmitter
  • Issue #2906 - Controller not removed from DB controller store when removed from controller
  • Issue #2922 - Validate node address before adding to cluster
  • Issue #2932 - Fix router data model 'create public key' related errors
  • Issue #2919 - Make xgress pluggable, so it can be used from the SDK
  • Issue #2955 - Extract xgress inspection types
  • Issue #2954 - Encapsulate xgress metrics
  • Issue #2952 - Remove global payload ingester
  • Issue #2951 - Remove global xgress retransmitter
  • Issue #2950 - Move router specific xgress code to a new xgress_router package
  • Issue #2920 - Make xgress acker configurable