From 15f85b27a77b12b90746dc6b2066c2fb053e2305 Mon Sep 17 00:00:00 2001
From: Nicola Moretto <nicola.moretto@mia-care.io>
Date: Tue, 29 Sep 2026 11:11:33 +0200
Subject: [PATCH] Sync GitLab doc

---
 .../kafka2rest-service/02_configuration.md       | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/docs/runtime-components/plugins/kafka2rest-service/02_configuration.md b/docs/runtime-components/plugins/kafka2rest-service/02_configuration.md
index 34f589a8bd..22dee4e853 100644
--- a/docs/runtime-components/plugins/kafka2rest-service/02_configuration.md
+++ b/docs/runtime-components/plugins/kafka2rest-service/02_configuration.md
@@ -20,6 +20,7 @@ an instance of `Kafka2Rest` service.
 - `TOPICS_REST_CONFIG_PATH`: the path where is located the _kafka-topic_:_base-url_ configuration map
 - `PATH_PROCESSORS_PATH`: the path where is located the path processors Javascript file
 - `BODY_PROCESSORS_PATH`: the path where is located the request body processors Javascript file
+- `HEADER_PROCESSORS_PATH`: the path where is located the request header processors Javascript file
 - `VALIDATOR_PROCESSORS_PATH`: the path where is located the message validator processors Javascript file 
 - `KAFKA_CLIENT_ID`: the identifier which can be employed to recognize this service within Kafka environment
 - `KAFKA_GROUP_ID`: the consumer group identifier employed by the service to read messages from Kafka
@@ -43,17 +44,16 @@ Here is provided the JSON schema that defines the configuration for each topic
   "type": "object",
   "required": [
     "baseUrl",
-    "messageSchema",
     "pathProcessor",
     "bodyProcessor"
   ],
   "properties": {
     "authentication": {
-        "type": "string",
-        "enum": ["none", "basic", "privateKeyJwt"],
-        "default": "none",
-        "description": "specify (optionally) the way the service should request a token to the client credentials to authenticate the request to the target url"
-      },
+      "type": "string",
+      "enum": ["none", "basic", "privateKeyJwt"],
+      "default": "none",
+      "description": "specify (optionally) the way the service should request a token to the client credentials to authenticate the request to the target url"
+    },
     "baseUrl": {
       "type": "string",
       "description": "the target base url onto which requests should be performed. This MUST terminate with a /"
@@ -70,6 +70,10 @@ Here is provided the JSON schema that defines the configuration for each topic
       "type": "string",
       "description": "the name of a body processor to be employed to generate the request body - selected from one of the available in bodyProcessors file"
     },
+    "headerProcessor": {
+      "type": "string",
+      "description": "the name of a header processor to be employed to generate the request headers - selected from one of the available in headerProcessors file"
+    },
     "validatorProcessor": {
       "type": "string",
       "description": "the name of a validator processor to be employed to filter invalid message - selected from one of the available in validatorProcessor file"