You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Gabor Somogyi (JIRA)" <ji...@apache.org> on 2018/12/10 13:42:00 UTC

[jira] [Updated] (SPARK-26322) Simplify kafka delegation token sasl.mechanism configuration

     [ https://issues.apache.org/jira/browse/SPARK-26322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabor Somogyi updated SPARK-26322:
----------------------------------
    Description: 
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.


  was:
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.



> 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
>            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 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org