[
https://issues.apache.org/jira/browse/KAFKA-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197602#comment-16197602
]
Ewen Cheslack-Postava commented on KAFKA-4029:
----------------------------------------------
I think the KIP's goal of keeping the interface consistent despite the fact we
don't have specifically a REST API with SSL yet is a good idea. Hopefully the
basics of just getting a secured, encrypted connection should be mostly
straightforward.
Something that might be missing from the KIP so far is discussion of
authorization / REST API ACLs. It definitely doesn't need to be implemented
together, but might be worth at least mentioning what we *aren't* doing even
though there is already demand for it.
> SSL support for Connect REST API
> --------------------------------
>
> Key: KAFKA-4029
> URL: https://issues.apache.org/jira/browse/KAFKA-4029
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Reporter: Ewen Cheslack-Postava
> Assignee: Jakub Scholz
>
> Currently the Connect REST API only supports http. We should also add SSL
> support so access to the REST API can be secured.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
