spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (SPARK-26322) Simplify kafka delegation token sasl.mechanism configuration
Date Mon, 10 Dec 2018 19:19:00 GMT


ASF GitHub Bot commented on SPARK-26322:

dongjoon-hyun commented on a change in pull request #23274: [SPARK-26322][SS] Add spark.kafka.token.sasl.mechanism
to ease delegation token configuration.

 File path: docs/
 @@ -642,9 +642,9 @@ This way the application can be configured via Spark parameters and may
not need
 configuration (Spark can use Kafka's dynamic JAAS configuration feature). For further information
 about delegation tokens, see [Kafka delegation token docs](
-The process is initiated by Spark's Kafka delegation token provider. When `spark.kafka.bootstrap.servers`,
+The process is initiated by Spark's Kafka delegation token provider. When `spark.kafka.bootstrap.servers`
 Spark considers the following log in options, in order of preference:
-- **JAAS login configuration**
+- **JAAS login configuration**, please see example below.
 Review comment:
   Hi, @gaborgsomogyi . Which example is this pointing? Previous examples seems to be removed.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Simplify kafka delegation token sasl.mechanism configuration
> ------------------------------------------------------------
>                 Key: SPARK-26322
>                 URL:
>             Project: Spark
>          Issue Type: Improvement
>          Components: Structured Streaming
>    Affects Versions: 3.0.0
>            Reporter: Gabor Somogyi
>            Priority: Major
> When Kafka delegation token obtained, SCRAM sasl.mechanism has to be configured for authentication.
This can be configured on the related source/sink which is inconvenient from user perspective.
Such granularity is not required and this configuration can be implemented with one central
> Kafka now supports 2 SCRAM related sasl.mechanism:
> - SCRAM-SHA-256
> - SCRAM-SHA-512
> and these are configured on brokers, which makes this configuration global.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message