[
https://issues.apache.org/jira/browse/KAFKA-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhu fangbo resolved KAFKA-5558.
-------------------------------
Resolution: Fixed
this is not a bug
> can not connect to the unsecure port after config SASL/PLAIN
> ------------------------------------------------------------
>
> Key: KAFKA-5558
> URL: https://issues.apache.org/jira/browse/KAFKA-5558
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 0.10.1.1
> Reporter: zhu fangbo
>
> Dear All,
> I followed modifying sasl mechanism in a running cluster to set a cluster
> with one broker using SASL/PLAIN to authorize client. here are configurations：
> server config
> server.properties：
> listeners=PLAINTEXT://:9093,SASL_PLAINTEXT://:9094
> security.inter.broker.protocol=SASL_PLAINTEXT
> sasl.mechanism.inter.broker.protocol=PLAIN
> sasl.enabled.mechanisms=PLAIN
> authorizer.class.name = kafka.security.auth.SimpleAclAuthorizer
> super.users=User:admin
> kafka_server_jaas.conf：
> KafkaServer {
> org.apache.kafka.common.security.plain.PlainLoginModule required
> username="admin"
> password="admin"
> user_admin="admin"
> user_alice="alice";
> };
> My producer configured with security.protocol=SASL_PLAINTEXT and correct
> jass.conf can work well when I connect to the secure port(9094)，but when I
> use the default security.protocol and connect to unsecure port(9093), the
> producer can not fetch metadata：
> DEBUG 17:18:10 kafka-producer-network-thread | producer-1 [NetworkClient]
> Sending metadata request {topics=[test]} to node -1
> WARN 17:18:10 kafka-producer-network-thread | producer-1 [NetworkClient]
> Error while fetching metadata with correlation id 0 :
> {test=UNKNOWN_TOPIC_OR_PARTITION}
> DEBUG 17:18:10 kafka-producer-network-thread | producer-1 [NetworkClient]
> Sending metadata request {topics=[test]} to node 1
> WARN 17:18:10 kafka-producer-network-thread | producer-1 [NetworkClient]
> Error while fetching metadata with correlation id 2 :
> {test=UNKNOWN_TOPIC_OR_PARTITION}
> Why the unsecure port can not be connected after config sasl authorization?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
