[
https://issues.apache.org/jira/browse/KAFKA-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823306#comment-16823306
]
Magesh kumar Nandakumar commented on KAFKA-8276:
------------------------------------------------
[~callmkarthik] I believe this is probably not a Kafka issue and should likely
be created against the Confluent Schema Registry project.
> Schema Registry Security settings as Props
> ------------------------------------------
>
> Key: KAFKA-8276
> URL: https://issues.apache.org/jira/browse/KAFKA-8276
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Affects Versions: 1.0.0, 2.0.0, 2.2.0
> Reporter: Karthik Murugesan
> Priority: Major
> Fix For: 1.0.0, 1.0.1, 1.1.0, 2.0.0, 2.1.0, 2.2.0, 2.1.1
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Take Schema Registry Security properties from the Properties File for C3, and
> from the Producer/Consumer Properties instead of setting it as JVM Props
> (-Djavax.net.ssl.*). This forces devs to import the certs to the cacerts of
> jvm keystore.
> confluent.controlcenter.schema.registry.url=https:/schema.registry.local.com:8081
> confluent.controlcenter.schema.registry.security.protocol=SSL
>
> confluent.controlcenter.schema.registry.ssl.keystore.location=/var/private/ssl/Keystore.jks
> confluent.controlcenter.schema.registry.ssl.keystore.password=****
>
> confluent.controlcenter.schema.registry.ssl.truststore.location=/var/private/ssl/Truststore.jks
> confluent.controlcenter.schema.registry.ssl.truststore.password=****
> confluent.controlcenter.schema.registry.ssl.key.password=****
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
