kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration
Date Tue, 15 Nov 2016 12:10:58 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666982#comment-15666982
] 

Ismael Juma commented on KAFKA-4406:
------------------------------------

[~rsivaram] beat me to it. I share the concern about setting a JVM-wide setting via a Kafka
config.

> Add support for custom Java Security Providers in configuration
> ---------------------------------------------------------------
>
>                 Key: KAFKA-4406
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4406
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.10.0.1
>            Reporter: Magnus Reftel
>            Priority: Minor
>
> Currently, the only way to add a custom security provider is though adding a -Djava.security.properties=<filename>
option to the command line, e.g. though KAFKA_OPTS. It would be more convenient if this could
be done though the config file, like all the other SSL related options.
> I propose adding a new configuration option, ssl.provider.classes, which holds a list
of names of security provider classes that will be loaded, instantiated, and added before
creating SSL contexts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message