[
https://issues.apache.org/jira/browse/SPARK-26322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Vanzin resolved SPARK-26322.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 23274
[https://github.com/apache/spark/pull/23274]
> Simplify kafka delegation token sasl.mechanism configuration
> ------------------------------------------------------------
>
> Key: SPARK-26322
> URL: https://issues.apache.org/jira/browse/SPARK-26322
> Project: Spark
> Issue Type: Improvement
> Components: Structured Streaming
> Affects Versions: 3.0.0
> Reporter: Gabor Somogyi
> Assignee: Gabor Somogyi
> Priority: Major
> Fix For: 3.0.0
>
>
> 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
> parameter.
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
