This is an automated email from the ASF dual-hosted git repository.

oscerd pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git


The following commit(s) were added to refs/heads/main by this push:
     new 17f036926 chore: kafka-sink, kafka-batch-source and 
ceph-event-based-source require an explicit saslAuthType (#3144) (#3185)
17f036926 is described below

commit 17f03692624e3e0b870973be12b80af88a818164
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Nov 18 10:00:18 2026 +0100

    chore: kafka-sink, kafka-batch-source and ceph-event-based-source require 
an explicit saslAuthType (#3144) (#3185)
    
    As kafka-source since #3069 (Fix #2970): saslAuthType has no default and is
    required, so a Kafka Kamelet never connects without security unless asked
    with saslAuthType: NONE. Breaking change: a route or Pipe without
    saslAuthType now fails at startup with "the following mandatory parameters
    must be provided: saslAuthType"; add saslAuthType: NONE to keep the old
    behaviour. The itest routes and the kafka-sink doc example set it.
    
    Co-authored-by: Claude Opus 5.5 <[email protected]>
---
 docs/modules/ROOT/partials/kafka-batch-source-description.adoc      | 4 ++--
 docs/modules/ROOT/partials/kafka-sink-description.adoc              | 3 ++-
 kamelets/ceph-event-based-source.kamelet.yaml                       | 6 +++---
 kamelets/kafka-batch-source.kamelet.yaml                            | 6 +++---
 kamelets/kafka-sink.kamelet.yaml                                    | 6 +++---
 .../camel-kamelets/src/main/resources/META-INF/kamelets-index.json  | 6 +++---
 .../main/resources/kamelets/ceph-event-based-source.kamelet.yaml    | 6 +++---
 .../src/main/resources/kamelets/kafka-batch-source.kamelet.yaml     | 6 +++---
 .../src/main/resources/kamelets/kafka-sink.kamelet.yaml             | 6 +++---
 .../src/test/resources/kafka/kafka-router-route.yaml                | 1 +
 .../src/test/resources/kafka/kafka-sink-route.yaml                  | 1 +
 11 files changed, 27 insertions(+), 24 deletions(-)

diff --git a/docs/modules/ROOT/partials/kafka-batch-source-description.adoc 
b/docs/modules/ROOT/partials/kafka-batch-source-description.adoc
index 85cdbe61c..7f2650001 100644
--- a/docs/modules/ROOT/partials/kafka-batch-source-description.adoc
+++ b/docs/modules/ROOT/partials/kafka-batch-source-description.adoc
@@ -2,8 +2,8 @@
 
 === Authentication methods
 
-The `saslAuthType` option chooses how the Kamelet logs in to Kafka, as for 
`kafka-source`. The
-default `NONE` connects with no login and no TLS, as a local Kafka expects.
+The `saslAuthType` option chooses how the Kamelet logs in to Kafka, as for 
`kafka-source`. It has
+no default and must be set; `NONE` connects with no login and no TLS, as a 
local Kafka expects.
 
 === Output format
 
diff --git a/docs/modules/ROOT/partials/kafka-sink-description.adoc 
b/docs/modules/ROOT/partials/kafka-sink-description.adoc
index bf96e8bea..75a69807d 100644
--- a/docs/modules/ROOT/partials/kafka-sink-description.adoc
+++ b/docs/modules/ROOT/partials/kafka-sink-description.adoc
@@ -8,7 +8,7 @@ leave the others empty.
 [width="100%",cols="1,3",options="header"]
 |===
 | `saslAuthType` | Options to set
-| `NONE` (default) | None. No login and no TLS, as a local Kafka expects.
+| `NONE` | None. No login and no TLS, as a local Kafka expects.
 | `PLAIN`, `SCRAM_SHA_256`, `SCRAM_SHA_512` | `saslUsername` and 
`saslPassword`.
 | `SSL` | `sslTruststoreLocation` and `sslTruststorePassword`; for mutual TLS 
also `sslKeystoreLocation`, `sslKeystorePassword` and `sslKeyPassword`.
 | `OAUTH` | `oauthClientId`, `oauthClientSecret` and `oauthTokenEndpointUri`; 
`oauthScope` when the provider asks for one.
@@ -38,4 +38,5 @@ The route below sends a JSON order every ten seconds to the 
`orders` topic, with
             parameters:
               bootstrapServers: "localhost:9092"
               topic: orders
+              saslAuthType: NONE
 ----
diff --git a/kamelets/ceph-event-based-source.kamelet.yaml 
b/kamelets/ceph-event-based-source.kamelet.yaml
index 515655226..17abaadfe 100644
--- a/kamelets/ceph-event-based-source.kamelet.yaml
+++ b/kamelets/ceph-event-based-source.kamelet.yaml
@@ -37,10 +37,11 @@ spec:
 
       Output: the body is the notification as JSON text, unchanged: a 
`Records` array that gives the event name (such as `ObjectCreated:Put`), the 
bucket name and the key of the file. The headers `ceph-event-id`, 
`ceph-opaque-data`, `ceph-object-metadata` and `ceph-object-tags` give the 
fields Ceph adds to the event; metadata and tags are a List of entries with a 
`key` and a `val`. Each header is also set with a `ce-` name, such as 
`ce-cepheventid`. With `getObject` true, the body of an  [...]
 
-      Good to know: the notification and its Kafka topic are set up on the 
Ceph side; this Kamelet only reads the topic. A record that is not a Ceph 
notification (without a `Records` array) fails. It connects to Kafka with no 
login and no TLS unless `saslAuthType` says otherwise. Without `consumerGroup`, 
each start uses a new group, so with the default `autoOffsetReset` of `latest` 
the events sent while it was stopped are not read.
+      Good to know: the notification and its Kafka topic are set up on the 
Ceph side; this Kamelet only reads the topic. A record that is not a Ceph 
notification (without a `Records` array) fails. `saslAuthType` has no default 
and must be set; `NONE` connects to Kafka with no login and no TLS. Without 
`consumerGroup`, each start uses a new group, so with the default 
`autoOffsetReset` of `latest` the events sent while it was stopped are not read.
     required:
       - topic
       - bootstrapServers
+      - saslAuthType
     type: object
     properties:
       topic:
@@ -66,9 +67,8 @@ spec:
         enum: ["latest", "earliest", "none"]
       saslAuthType:
         title: Authentication Type
-        description: How to log in to Kafka. `NONE` connects with no login and 
no TLS, as a local Kafka expects; `PLAIN`, `SCRAM_SHA_256` and `SCRAM_SHA_512` 
log in with `saslUsername` and `saslPassword`.
+        description: How to log in to Kafka. It has no default and must be 
set. `NONE` connects with no login and no TLS, as a local Kafka expects; 
`PLAIN`, `SCRAM_SHA_256` and `SCRAM_SHA_512` log in with `saslUsername` and 
`saslPassword`.
         type: string
-        default: NONE
         enum: ["NONE", "PLAIN", "SCRAM_SHA_256", "SCRAM_SHA_512", "SSL", 
"OAUTH", "AWS_MSK_IAM", "KERBEROS"]
       saslUsername:
         title: Username
diff --git a/kamelets/kafka-batch-source.kamelet.yaml 
b/kamelets/kafka-batch-source.kamelet.yaml
index a22f7bee7..998eb6626 100644
--- a/kamelets/kafka-batch-source.kamelet.yaml
+++ b/kamelets/kafka-batch-source.kamelet.yaml
@@ -37,10 +37,11 @@ spec:
 
       Output: the body is a List with one entry per record, up to `batchSize`. 
Each entry is a message of its own, with the value of the record as its body 
(text), and the key, offset and timestamp of the record in its `CamelKafkaKey`, 
`CamelKafkaOffset` and `CamelKafkaTimestamp` headers. The record headers are in 
the entries too, as bytes. The message itself has the `CamelKafkaTopic` and 
`CamelKafkaPartition` headers. The `kafka-topic`, `kafka-key` and other headers 
of `kafka-source` ar [...]
 
-      Good to know: with the default `saslAuthType` of `NONE`, it connects 
with no login and no TLS. To save the position in Kafka only once a batch was 
handled, set `allowManualCommit` to true and `autoCommitEnable` to false, and 
end the flow with `kafka-batch-manual-commit-action`. A new consumer group 
starts at the newest records, unless `autoOffsetReset` is `earliest`. Without 
`consumerGroup`, every start uses a new group, so the records sent while the 
integration was stopped are skipped.
+      Good to know: `saslAuthType` has no default and must be set; `NONE` 
connects with no login and no TLS. To save the position in Kafka only once a 
batch was handled, set `allowManualCommit` to true and `autoCommitEnable` to 
false, and end the flow with `kafka-batch-manual-commit-action`. A new consumer 
group starts at the newest records, unless `autoOffsetReset` is `earliest`. 
Without `consumerGroup`, every start uses a new group, so the records sent 
while the integration was stopped [...]
     required:
       - topic
       - bootstrapServers
+      - saslAuthType
     type: object
     properties:
       topic:
@@ -55,9 +56,8 @@ spec:
         example: "broker1:9092,broker2:9092"
       saslAuthType:
         title: Authentication Type
-        description: "How to log in to Kafka. The default `NONE` connects with 
no login and no TLS, as a local Kafka expects; `PLAIN`, `SCRAM_SHA_256` and 
`SCRAM_SHA_512` log in with `saslUsername` and `saslPassword`; `SSL` connects 
over TLS and logs in with the client certificate in `sslKeystoreLocation`, when 
set; `OAUTH` logs in with the `oauth` options; `AWS_MSK_IAM` (Amazon MSK) and 
`KERBEROS` take their credentials from the environment the integration runs in. 
All types except `NON [...]
+        description: "How to log in to Kafka. It has no default and must be 
set. `NONE` connects with no login and no TLS, as a local Kafka expects; 
`PLAIN`, `SCRAM_SHA_256` and `SCRAM_SHA_512` log in with `saslUsername` and 
`saslPassword`; `SSL` connects over TLS and logs in with the client certificate 
in `sslKeystoreLocation`, when set; `OAUTH` logs in with the `oauth` options; 
`AWS_MSK_IAM` (Amazon MSK) and `KERBEROS` take their credentials from the 
environment the integration runs in [...]
         type: string
-        default: NONE
         enum: ["NONE", "PLAIN", "SCRAM_SHA_256", "SCRAM_SHA_512", "SSL", 
"OAUTH", "AWS_MSK_IAM", "KERBEROS"]
       saslUsername:
         title: Username
diff --git a/kamelets/kafka-sink.kamelet.yaml b/kamelets/kafka-sink.kamelet.yaml
index 02b08d532..201ceedec 100644
--- a/kamelets/kafka-sink.kamelet.yaml
+++ b/kamelets/kafka-sink.kamelet.yaml
@@ -39,10 +39,11 @@ spec:
 
       Output: the message is unchanged.
 
-      Good to know: with the default `saslAuthType` of `NONE`, it connects 
with no login and no TLS, as a local Kafka expects. A managed Kafka service 
needs one of the other types.
+      Good to know: `saslAuthType` has no default and must be set; `NONE` 
connects with no login and no TLS, as a local Kafka expects. A managed Kafka 
service needs one of the other types.
     required:
       - topic
       - bootstrapServers
+      - saslAuthType
     type: object
     properties:
       topic:
@@ -57,9 +58,8 @@ spec:
         example: "broker1:9092,broker2:9092"
       saslAuthType:
         title: Authentication Type
-        description: Authentication type to use. Use NONE for no 
authentication, PLAIN or SCRAM_SHA_256/SCRAM_SHA_512 for username/password, SSL 
for certificate-based, OAUTH for OAuth 2.0, AWS_MSK_IAM for MSK, or KERBEROS 
for Kerberos.
+        description: "How to log in to Kafka. It has no default and must be 
set. `NONE` connects with no login and no TLS, as a local Kafka expects; 
`PLAIN`, `SCRAM_SHA_256` and `SCRAM_SHA_512` log in with `saslUsername` and 
`saslPassword`; `SSL` connects over TLS and logs in with the client certificate 
in `sslKeystoreLocation`, when set; `OAUTH` logs in with the `oauth` options; 
`AWS_MSK_IAM` (Amazon MSK) and `KERBEROS` take their credentials from the 
environment the integration runs in [...]
         type: string
-        default: NONE
         enum: ["NONE", "PLAIN", "SCRAM_SHA_256", "SCRAM_SHA_512", "SSL", 
"OAUTH", "AWS_MSK_IAM", "KERBEROS"]
       saslUsername:
         title: Username
diff --git 
a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json 
b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
index f75ed8abd..0cddeadca 100644
--- a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
+++ b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
@@ -515,7 +515,7 @@
     "supportLevel" : "Preview",
     "title" : "Ceph Event Based Source",
     "summary" : "Receives the bucket notifications that a Ceph Object Gateway 
sends to a Kafka topic, one message per event, such as a file added to or 
deleted from a bucket.",
-    "description" : "Receives the bucket notifications that a Ceph Object 
Gateway sends to a Kafka topic, one message per event, such as a file added to 
or deleted from a bucket.\n\nUse it to react as soon as a file is uploaded to 
or removed from a Ceph bucket, without reading the bucket over and over. Set 
`getObject` to true to receive the content of each new file. To read and remove 
the files of a bucket instead, use `ceph-source`.\n\nOutput: the body is the 
notification as JSON text,  [...]
+    "description" : "Receives the bucket notifications that a Ceph Object 
Gateway sends to a Kafka topic, one message per event, such as a file added to 
or deleted from a bucket.\n\nUse it to react as soon as a file is uploaded to 
or removed from a Ceph bucket, without reading the bucket over and over. Set 
`getObject` to true to receive the content of each new file. To read and remove 
the files of a bucket instead, use `ceph-source`.\n\nOutput: the body is the 
notification as JSON text,  [...]
     "group" : "Ceph",
     "namespace" : "Cloud",
     "provider" : "Apache Software Foundation"
@@ -1395,7 +1395,7 @@
     "supportLevel" : "Stable",
     "title" : "Kafka Batch Source",
     "summary" : "Receives records from one or more topics in Apache Kafka in 
batches, as one message that holds a list of up to `batchSize` records.",
-    "description" : "Receives records from one or more topics in Apache Kafka 
in batches, as one message that holds a list of up to `batchSize` 
records.\n\nUse it to handle many records at once, for example to write them to 
a database in one go, or to save the position in Kafka only once a whole batch 
was handled. To handle one record at a time use `kafka-source`.\n\nOutput: the 
body is a List with one entry per record, up to `batchSize`. Each entry is a 
message of its own, with the valu [...]
+    "description" : "Receives records from one or more topics in Apache Kafka 
in batches, as one message that holds a list of up to `batchSize` 
records.\n\nUse it to handle many records at once, for example to write them to 
a database in one go, or to save the position in Kafka only once a whole batch 
was handled. To handle one record at a time use `kafka-source`.\n\nOutput: the 
body is a List with one entry per record, up to `batchSize`. Each entry is a 
message of its own, with the valu [...]
     "group" : "Kafka",
     "namespace" : "Kafka",
     "provider" : "Apache Software Foundation"
@@ -1445,7 +1445,7 @@
     "supportLevel" : "Stable",
     "title" : "Kafka Sink",
     "summary" : "Sends each message as a record to a topic in Apache Kafka, or 
in a Kafka-compatible service such as Amazon MSK, Confluent Cloud or Redpanda.",
-    "description" : "Sends each message as a record to a topic in Apache 
Kafka, or in a Kafka-compatible service such as Amazon MSK, Confluent Cloud or 
Redpanda.\n\nUse it to publish events or data for other applications to read, 
such as orders, sensor readings or changes from a database. When the records 
must follow a schema kept in a schema registry, use one of the 
`kafka-*-registry-*` sinks instead.\n\nInput: the body becomes the value of the 
record, as text. Turn structured data such [...]
+    "description" : "Sends each message as a record to a topic in Apache 
Kafka, or in a Kafka-compatible service such as Amazon MSK, Confluent Cloud or 
Redpanda.\n\nUse it to publish events or data for other applications to read, 
such as orders, sensor readings or changes from a database. When the records 
must follow a schema kept in a schema registry, use one of the 
`kafka-*-registry-*` sinks instead.\n\nInput: the body becomes the value of the 
record, as text. Turn structured data such [...]
     "group" : "Kafka",
     "namespace" : "Kafka",
     "provider" : "Apache Software Foundation"
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/ceph-event-based-source.kamelet.yaml
 
b/library/camel-kamelets/src/main/resources/kamelets/ceph-event-based-source.kamelet.yaml
index 515655226..17abaadfe 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/ceph-event-based-source.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/ceph-event-based-source.kamelet.yaml
@@ -37,10 +37,11 @@ spec:
 
       Output: the body is the notification as JSON text, unchanged: a 
`Records` array that gives the event name (such as `ObjectCreated:Put`), the 
bucket name and the key of the file. The headers `ceph-event-id`, 
`ceph-opaque-data`, `ceph-object-metadata` and `ceph-object-tags` give the 
fields Ceph adds to the event; metadata and tags are a List of entries with a 
`key` and a `val`. Each header is also set with a `ce-` name, such as 
`ce-cepheventid`. With `getObject` true, the body of an  [...]
 
-      Good to know: the notification and its Kafka topic are set up on the 
Ceph side; this Kamelet only reads the topic. A record that is not a Ceph 
notification (without a `Records` array) fails. It connects to Kafka with no 
login and no TLS unless `saslAuthType` says otherwise. Without `consumerGroup`, 
each start uses a new group, so with the default `autoOffsetReset` of `latest` 
the events sent while it was stopped are not read.
+      Good to know: the notification and its Kafka topic are set up on the 
Ceph side; this Kamelet only reads the topic. A record that is not a Ceph 
notification (without a `Records` array) fails. `saslAuthType` has no default 
and must be set; `NONE` connects to Kafka with no login and no TLS. Without 
`consumerGroup`, each start uses a new group, so with the default 
`autoOffsetReset` of `latest` the events sent while it was stopped are not read.
     required:
       - topic
       - bootstrapServers
+      - saslAuthType
     type: object
     properties:
       topic:
@@ -66,9 +67,8 @@ spec:
         enum: ["latest", "earliest", "none"]
       saslAuthType:
         title: Authentication Type
-        description: How to log in to Kafka. `NONE` connects with no login and 
no TLS, as a local Kafka expects; `PLAIN`, `SCRAM_SHA_256` and `SCRAM_SHA_512` 
log in with `saslUsername` and `saslPassword`.
+        description: How to log in to Kafka. It has no default and must be 
set. `NONE` connects with no login and no TLS, as a local Kafka expects; 
`PLAIN`, `SCRAM_SHA_256` and `SCRAM_SHA_512` log in with `saslUsername` and 
`saslPassword`.
         type: string
-        default: NONE
         enum: ["NONE", "PLAIN", "SCRAM_SHA_256", "SCRAM_SHA_512", "SSL", 
"OAUTH", "AWS_MSK_IAM", "KERBEROS"]
       saslUsername:
         title: Username
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-source.kamelet.yaml
 
b/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-source.kamelet.yaml
index a22f7bee7..998eb6626 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-source.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-source.kamelet.yaml
@@ -37,10 +37,11 @@ spec:
 
       Output: the body is a List with one entry per record, up to `batchSize`. 
Each entry is a message of its own, with the value of the record as its body 
(text), and the key, offset and timestamp of the record in its `CamelKafkaKey`, 
`CamelKafkaOffset` and `CamelKafkaTimestamp` headers. The record headers are in 
the entries too, as bytes. The message itself has the `CamelKafkaTopic` and 
`CamelKafkaPartition` headers. The `kafka-topic`, `kafka-key` and other headers 
of `kafka-source` ar [...]
 
-      Good to know: with the default `saslAuthType` of `NONE`, it connects 
with no login and no TLS. To save the position in Kafka only once a batch was 
handled, set `allowManualCommit` to true and `autoCommitEnable` to false, and 
end the flow with `kafka-batch-manual-commit-action`. A new consumer group 
starts at the newest records, unless `autoOffsetReset` is `earliest`. Without 
`consumerGroup`, every start uses a new group, so the records sent while the 
integration was stopped are skipped.
+      Good to know: `saslAuthType` has no default and must be set; `NONE` 
connects with no login and no TLS. To save the position in Kafka only once a 
batch was handled, set `allowManualCommit` to true and `autoCommitEnable` to 
false, and end the flow with `kafka-batch-manual-commit-action`. A new consumer 
group starts at the newest records, unless `autoOffsetReset` is `earliest`. 
Without `consumerGroup`, every start uses a new group, so the records sent 
while the integration was stopped [...]
     required:
       - topic
       - bootstrapServers
+      - saslAuthType
     type: object
     properties:
       topic:
@@ -55,9 +56,8 @@ spec:
         example: "broker1:9092,broker2:9092"
       saslAuthType:
         title: Authentication Type
-        description: "How to log in to Kafka. The default `NONE` connects with 
no login and no TLS, as a local Kafka expects; `PLAIN`, `SCRAM_SHA_256` and 
`SCRAM_SHA_512` log in with `saslUsername` and `saslPassword`; `SSL` connects 
over TLS and logs in with the client certificate in `sslKeystoreLocation`, when 
set; `OAUTH` logs in with the `oauth` options; `AWS_MSK_IAM` (Amazon MSK) and 
`KERBEROS` take their credentials from the environment the integration runs in. 
All types except `NON [...]
+        description: "How to log in to Kafka. It has no default and must be 
set. `NONE` connects with no login and no TLS, as a local Kafka expects; 
`PLAIN`, `SCRAM_SHA_256` and `SCRAM_SHA_512` log in with `saslUsername` and 
`saslPassword`; `SSL` connects over TLS and logs in with the client certificate 
in `sslKeystoreLocation`, when set; `OAUTH` logs in with the `oauth` options; 
`AWS_MSK_IAM` (Amazon MSK) and `KERBEROS` take their credentials from the 
environment the integration runs in [...]
         type: string
-        default: NONE
         enum: ["NONE", "PLAIN", "SCRAM_SHA_256", "SCRAM_SHA_512", "SSL", 
"OAUTH", "AWS_MSK_IAM", "KERBEROS"]
       saslUsername:
         title: Username
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/kafka-sink.kamelet.yaml 
b/library/camel-kamelets/src/main/resources/kamelets/kafka-sink.kamelet.yaml
index 02b08d532..201ceedec 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/kafka-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/kafka-sink.kamelet.yaml
@@ -39,10 +39,11 @@ spec:
 
       Output: the message is unchanged.
 
-      Good to know: with the default `saslAuthType` of `NONE`, it connects 
with no login and no TLS, as a local Kafka expects. A managed Kafka service 
needs one of the other types.
+      Good to know: `saslAuthType` has no default and must be set; `NONE` 
connects with no login and no TLS, as a local Kafka expects. A managed Kafka 
service needs one of the other types.
     required:
       - topic
       - bootstrapServers
+      - saslAuthType
     type: object
     properties:
       topic:
@@ -57,9 +58,8 @@ spec:
         example: "broker1:9092,broker2:9092"
       saslAuthType:
         title: Authentication Type
-        description: Authentication type to use. Use NONE for no 
authentication, PLAIN or SCRAM_SHA_256/SCRAM_SHA_512 for username/password, SSL 
for certificate-based, OAUTH for OAuth 2.0, AWS_MSK_IAM for MSK, or KERBEROS 
for Kerberos.
+        description: "How to log in to Kafka. It has no default and must be 
set. `NONE` connects with no login and no TLS, as a local Kafka expects; 
`PLAIN`, `SCRAM_SHA_256` and `SCRAM_SHA_512` log in with `saslUsername` and 
`saslPassword`; `SSL` connects over TLS and logs in with the client certificate 
in `sslKeystoreLocation`, when set; `OAUTH` logs in with the `oauth` options; 
`AWS_MSK_IAM` (Amazon MSK) and `KERBEROS` take their credentials from the 
environment the integration runs in [...]
         type: string
-        default: NONE
         enum: ["NONE", "PLAIN", "SCRAM_SHA_256", "SCRAM_SHA_512", "SSL", 
"OAUTH", "AWS_MSK_IAM", "KERBEROS"]
       saslUsername:
         title: Username
diff --git 
a/tests/camel-kamelets-itest/src/test/resources/kafka/kafka-router-route.yaml 
b/tests/camel-kamelets-itest/src/test/resources/kafka/kafka-router-route.yaml
index db7b04ba9..7931e608a 100644
--- 
a/tests/camel-kamelets-itest/src/test/resources/kafka/kafka-router-route.yaml
+++ 
b/tests/camel-kamelets-itest/src/test/resources/kafka/kafka-router-route.yaml
@@ -40,4 +40,5 @@
             uri: "kamelet:kafka-sink"
             parameters:
               bootstrapServers: '{{kafka.bootstrapServers}}'
+              saslAuthType: NONE
               topic: dummy
diff --git 
a/tests/camel-kamelets-itest/src/test/resources/kafka/kafka-sink-route.yaml 
b/tests/camel-kamelets-itest/src/test/resources/kafka/kafka-sink-route.yaml
index 966b380d4..715922965 100644
--- a/tests/camel-kamelets-itest/src/test/resources/kafka/kafka-sink-route.yaml
+++ b/tests/camel-kamelets-itest/src/test/resources/kafka/kafka-sink-route.yaml
@@ -27,4 +27,5 @@
             uri: "kamelet:kafka-sink"
             parameters:
               bootstrapServers: '{{kafka.bootstrapServers}}'
+              saslAuthType: NONE
               topic: '{{kafka.topic}}'

Reply via email to