Vineet Saurabh created CAMEL-22624:
--------------------------------------
Summary: New Component: camel-azure-iothub for Idiomatic D2C, C2D,
and Twin Operations
Key: CAMEL-22624
URL: https://issues.apache.org/jira/browse/CAMEL-22624
Project: Camel
Issue Type: New Feature
Components: camel-azure
Reporter: Vineet Saurabh
Currently, Azure IoT Hub functionality is partially covered by the generic
{{camel-azure-eventhubs}} component, which only addresses the {*}built-in Event
Hubs-compatible endpoint{*}. This leads to significant architectural and
functional limitations when integrating from a backend service:
# *Limited Endpoint Access:* The Event Hubs component cannot access critical,
higher-level IoT Hub Service Endpoints required for two-way communication and
device management (e.g., Device Identity Registry, Cloud-to-Device messaging,
Direct Methods, and Device Twin updates).
# *D2C Telemetry Workarounds:* Sending D2C (Device-to-Cloud) telemetry from a
service backend (instead of a device client) requires non-standard manipulation
to correctly attribute the message to a specific device.
# *Authentication Complexity:* The current component does not natively manage
the necessary IoT Hub Service Policy authentication required for comprehensive
backend operations.
A dedicated {{camel-azure-iothub}} component is required to provide clean,
supported, and idiomatic integration for all major Azure IoT Hub features by
natively wrapping the {*}Azure IoT Hub Service SDK{*}.
*Key Features to be Supported:*
* *D2C Telemetry:* Cleanly send Device-to-Cloud messages from a service
backend.
* *C2D Commands:* Send Cloud-to-Device commands.
* *Device Twin:* Read, update, and manage Device Twin properties and tags.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
