1.10.0

1.10.0

New Features

• The JDBC and Mongo DB based registry implementations now support configuration of a regular expression that should
  be used to validate authentication identifiers (user names) of hashed-password credentials. Please refer to the
  corresponding Admin Guides for details.
• The Command Router component is now able to determine the state of protocol adapter instances, preventing command
  & control messages to be sent to already terminated adapter instances. Hono Kubernetes deployments where not all
  protocol adapters are part of the same Kubernetes cluster and namespace that the Command Router component is in,
  need to disable this feature via the hono.commandRouter.svc.kubernetesBasedAdapterInstanceStatusServiceEnabled
  property. Please refer to the Command Router Admin Guide for details.
• The authentication provider used to guard access to the Mongo DB based registry implementation's HTTP endpoint
  can now be configured using environment variables. Please refer to the registry's Admin Guide for details.
• The Registry Management API has been extended with an operation to delete all devices (including credentials) of a
  tenant. Both the Mongo DB and the JDBC based registry implementations support this operation.
• The protocol adapters and the Command Router component now by default report a set of metrics concerning the clients
  used for sending and receiving messages via Kafka. Please refer to the Hono Kafka Client Configuration Guide for
  additional information.

Fixes & Enhancements

• The Quarkus based variants of Hono's components now support configuring the Hot Rod client with a key and/or
  trust store in order to enable TLS secured connections to Infinispan servers and to authenticate using a
  client certificate.
• The MongoDB based DeviceManagementService erroneously removed the original device registration when trying to
  register a new device using the existing device's identifier. This has been fixed.
• The Mongo DB based registry implementation now uses a proper DB index to find credentials by type and authentication
  ID. This will speed up query execution significantly when there are a lot of devices registered for a tenant.
• The JDBC based device registry's get Credentials operation used by the protocol adapters now also supports
  matching credentials against a given client context.
• The device registry implementations did not return a JSON object in a response to a failed request as specified
  in the Device Registry Management API. This has been fixed.
• The MongoDB based registry erroneously rejected requests that would result in multiple tenants having an empty
  set of trusted CAs. This has been fixed.
• The ttl header in downstream messages with Kafka had been set in seconds instead of milliseconds, as defined
  by the API specification. This has been fixed.