[
https://issues.apache.org/jira/browse/KAFKA-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245972#comment-14245972
]
Joe Stein commented on KAFKA-1810:
----------------------------------
+1 I like this approach because you can better manage the brokers to have
resilience in their network environment for what hosts can connect to them.
This is an implementation of what KAFKA-1688 will be layering and making
pluggable. I also see overlap with
https://issues.apache.org/jira/browse/KAFKA-1786 and might be a good place to
start building that out too.
> Add IP Filtering / Whitelists-Blacklists
> -----------------------------------------
>
> Key: KAFKA-1810
> URL: https://issues.apache.org/jira/browse/KAFKA-1810
> Project: Kafka
> Issue Type: New Feature
> Components: core, network
> Reporter: Jeff Holoman
> Assignee: Jeff Holoman
> Priority: Minor
> Fix For: 0.8.3
>
>
> While longer-term goals of security in Kafka are on the roadmap there exists
> some value for the ability to restrict connection to Kafka brokers based on
> IP address. This is not intended as a replacement for security but more of a
> precaution against misconfiguration and to provide some level of control to
> Kafka administrators about who is reading/writing to their cluster.
> 1) In some organizations software administration vs o/s systems
> administration and network administration is disjointed and not well
> choreographed. Providing software administrators the ability to configure
> their platform relatively independently (after initial configuration) from
> Systems administrators is desirable.
> 2) Configuration and deployment is sometimes error prone and there are
> situations when test environments could erroneously read/write to production
> environments
> 3) An additional precaution against reading sensitive data is typically
> welcomed in most large enterprise deployments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
