1.12.0

New Features

• The Mongo DB based device registry now supports multiple tenants to use the same trust anchors for authenticating
  devices based on client certificates. The devices belonging to such tenants need to indicate the tenant identifier
  using the Server Name Indication extension during their TLS handshake with a protocol adapter. Please refer to the
  Device Registry Management API for details on how to configure tenants accordingly. Please refer to the protocol
  adapter user guides and the Device Identity concept page for details regarding device authentication based on client
  certificates.
• A Quarkus based variant of the MongoDB device registry has been added.

Fixes & Enhancements

• The device registry containers might not have started up properly when used with Kafka as the messaging
  infrastructure. This has been fixed.
• The MongoDB device registry did not accept HTTP endpoint credentials that worked with Hono <= 1.10 because
  password hashes were created in lower case instead of upper case. This has been fixed.
• The native executable of the Command Router component did not start when configured with an embedded cache.
  This has been fixed.
• There was an issue trying to send connection events concerning unauthenticated MQTT/AMQP devices. This has been fixed.

Deprecations

• The Spring Boot based variant of the MongoDB device registry has been deprecated and marked for removal in Hono 2.0.0.