You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Karthik Murugesan (JIRA)" <ji...@apache.org> on 2019/04/22 16:41:00 UTC

[jira] [Created] (KAFKA-8276) Schema Registry Security settings as Props

Karthik Murugesan created KAFKA-8276:
----------------------------------------

             Summary: 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: 2.2.0, 2.0.0, 1.0.0
            Reporter: Karthik Murugesan
             Fix For: 2.1.1, 2.2.0, 2.1.0, 2.0.0, 1.1.0, 1.0.1, 1.0.0


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)