Eclipse Hono 1.11.0

1.11.0

Description

This minor release introduces the following new features

  • The Authentication Server now also reports the hono.connections.attempts metric which counts the number of authentication attempts made by clients.
  • The JDBC DB based registry now also supports enforcement of registration limits configured at the tenant level. In particular, the maximum number of devices and the maximum number of credentials per device can be set in a tenant's registration-limits property. Please refer to the User Guide for details.
  • Kafka clients used by a component can now be configured individually instead of all clients of a type using the same configuration. The prefixes that are prepended to the configuration properties of the native Kafka client have changed. For existing configuration properties prefixed with hono.kafka.commonClientConfig properties, no change is needed. Other configurations with specific consumer/producer/admin client properties have to be adapted. Please refer to the Hono Kafka Client Configuration Guide for details.
  • The protocol adapters now include a ttl header/property in every message being forwarded, regardless of message type. This allows a consumer of a message to easily determine if the message should be processed or considered expired already. The device registry supports the definition of default ttl values for the different types of messages at both the tenant and device level. Please refer to the Tenant API for details regarding the corresponding default property names to use.
API Certification

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Architectural Issues

In addition to adding the new features described above, a lot of improvements regarding runtime behavior and stability have been made in the area of supporting Kafka as the messaging infrastructure. Based on these improvements, Kafka support is now fully supported and ready for production.

Security Issues

The log4shell security vulnerability in the Log4i 2 library has caused a lot of work for IT support personnel worldwide. Some of the third party components used by Hono depend on the Log4j 2 API. However, Hono was not and is not affected by log4shell because it does not use the Log4j runtime implementation.

Conforms To UI/UX Guidelines
Not verified
End of Life

The Spring Boot based implementations of the Protocol Adapters have been deprecated and marked for removal in Hono 2.0.0. The Quarkus based implementations are now the default variants.

The Kura protocol adapter which allowed Kura 3 based gateways to connect to Hono has been deprecated and marked for removal in Hono 2.0.0. Support for Kura version 4 and later is still available by means of Hono's standard MQTT adapter.