Table of Contents |
---|
Status
Current state: Under Discussion
...
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
Kafka Connect has a REST interface for managing and monitoring connectors. Currently this REST interface is using only plain HTTP without any encryption and authentication. This is not ideal because:
...
Extending the REST interface with support for SSL / TLS encryption and SSL / TLS client authentication could address these issues.
Proposed Change
This KIP proposes adding
Public Interfaces
- New class
org.apache.kafka.common.serialization.UUIDSerializer
which implements theSerializer<UUID>
interface - New class
org.apache.kafka.common.serialization.UUIDDeserializer
which implements theDeserializer<UUID>
interface - New method
static public Serde<UUID> UUID()
inorg.apache.kafka.common.serialization.Serdes
class - New subclass
UUIDSerde
inorg.apache.kafka.common.serialization.Serdes
which creates a new serde based on theUUIDSerializer
andUUIDDeserializer
classes
Migration Plan and Compatibility
This KIP is a new implementation and doesn't have any backwards compatibility issues or special requirements on migration from older versions. Existing Kafka Connect installation would work in the same way as before this change. Without the SSL configuration, the REST interface will continue to be configured as today - i.e. without SSL / TLS.
Rejected Alternatives
n/a