[
https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666957#comment-15666957
]
Rajini Sivaram commented on KAFKA-4406:
---------------------------------------
[~magnus.reftel] You will need to create a [Kafka Improvement
Proposal|https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals]
to add a new configuration parameter.
The other SSL configuration options change a property on the SSL context used
by Kafka. But this configuration is changing a JVM-wide setting. Since you can
call {{Security.addProvider()}} in your application or set
{{java.security.properties}} for the JVM without changing code, I am not sure
if a Kafka-specific option is really necessary.
> 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)
