LogoLogo
  • What is Kouncil?
  • Getting started
    • Installation
      • Deployment
      • Development
    • Configuration
      • Authentication
        • Local authentication
        • LDAP, LDAPS and AD authentication
        • SSO
          • GitHub
          • Okta
      • Authorization
      • SSL/TLS Configuration
        • Configuration
        • Kafka
          • TLS configuration
          • Broker SSL configuration
          • AWS MSK configuration
        • Schema Registry
          • SSL Configuration
          • SSL and Basic authentication
      • JMX
      • Logging
      • Websocket
      • Custom context path
      • Database
    • Features
    • FAQ
    • Roadmap
Powered by GitBook
On this page
Export as PDF
  1. Getting started
  2. Configuration
  3. SSL/TLS Configuration
  4. Schema Registry

SSL Configuration

WARNING

This configuration will be deprecated in version 1.9 and removed in the future. In version 1.9 this configuration will be used to preload your clusters.

Assuming your SchemaRegistry is secured and requires SSL for connection, you need to provide a client truststore that contains the CA's public certificate, and a keystore that includes both the client's private key and the CA-signed certificate.

kouncil:
  clusters:
    - name: transaction-cluster
      schemaRegistry:
        url: "https://schema.registry:8081"
        security:
          protocol: SSL
        ssl:
          truststore-location: file:///config/truststore/client.truststore.jks
          truststore-password: password
          trustStoreType: JKS
          keystore-location: file:///config/keystore/client.keystore.jks
          keystore-password: password
          key-password: password
          keyStoreType: JKS
      brokers:
        - host: 192.10.0.1
          port: 9092
PreviousSchema RegistryNextSSL and Basic authentication

Last updated 6 months ago