Hi everyone,
We are planning to restrict the set of connectors that can be used in our Camunda 8 environment to only those that have been verified by us.
One of the required connectors is a REST connector that must inject a proprietary authentication header into every outbound request (e.g., X‑Custom‑Token). The upstream Camunda REST connector does not provide this out‑of‑the‑box.
What we need:
Element template – a custom connector template that is visible in the Modeler (Desktop and Web)
Runtime extension – Java code that automatically adds the custom header to all HTTP calls executed by the connector.
Main Challenge:
We want to avoid “hard-forking” the connector code. If we upgrade Camunda (e.g., from 8.9 to 8.10) or if the upstream REST Connector repository is updated, we want to receive those updates seamlessly without having to manually merge or rewrite our custom logic.
What would be the recommended design for this? Is there a way to implement a “wrapper” or a “plugin” architecture that works for both the Desktop and Web Modeler?
Thanks in advance!