Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@kafka.apache.org
Date: Wed, 5 Jul 2017 09:40:00 +0000 (UTC)
From: "zhu fangbo (JIRA)" <jira@apache.org>
To: jira@kafka.apache.org
Message-ID: <JIRA.13084739.1499247576000.171798.1499247600301@Atlassian.JIRA>
In-Reply-To: <JIRA.13084739.1499247576000@Atlassian.JIRA>
References: <JIRA.13084739.1499247576000@Atlassian.JIRA> <JIRA.13084739.1499247576726@jira-lw-us.apache.org>
Subject: [jira] [Created] (KAFKA-5558) can not connect to the unsecure port
 after config SASL/PLAIN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 05 Jul 2017 09:40:06 -0000

zhu fangbo created KAFKA-5558:
---------------------------------

             Summary: can not connect to the unsecure port after config SAS=
L/PLAIN
                 Key: KAFKA-5558
                 URL: https://issues.apache.org/jira/browse/KAFKA-5558
             Project: Kafka
          Issue Type: New Feature
          Components: clients
    Affects Versions: 0.10.1.1
            Reporter: zhu fangbo


Dear All,=20
I followed modifying sasl mechanism in a running cluster to set a cluster w=
ith one broker using SASL/PLAIN to authorize client. here are configuration=
s=EF=BC=9A
server config
server.properties=EF=BC=9A
listeners=3DPLAINTEXT://:9093,SASL_PLAINTEXT://:9094
security.inter.broker.protocol=3DSASL_PLAINTEXT
sasl.mechanism.inter.broker.protocol=3DPLAIN
sasl.enabled.mechanisms=3DPLAIN
authorizer.class.name =3D kafka.security.auth.SimpleAclAuthorizer
super.users=3DUser:admin
kafka_server_jaas.conf=EF=BC=9A
KafkaServer {
    org.apache.kafka.common.security.plain.PlainLoginModule required
    username=3D"admin"
    password=3D"admin"
    user_admin=3D"admin"
    user_alice=3D"alice";
};
My producer configured with security.protocol=3DSASL_PLAINTEXT and correct =
jass.conf can work well when I connect to the secure port(9094)=EF=BC=8Cbut=
 when I use the default security.protocol and connect to unsecure port(9093=
), the producer can not fetch metadata=EF=BC=9A
DEBUG 17:18:10 kafka-producer-network-thread | producer-1 [NetworkClient] S=
ending metadata request {topics=3D[test]} to node -1
WARN 17:18:10 kafka-producer-network-thread | producer-1 [NetworkClient] Er=
ror while fetching metadata with correlation id 0 : {test=3DUNKNOWN_TOPIC_O=
R_PARTITION}
DEBUG 17:18:10 kafka-producer-network-thread | producer-1 [NetworkClient] S=
ending metadata request {topics=3D[test]} to node 1
WARN 17:18:10 kafka-producer-network-thread | producer-1 [NetworkClient] Er=
ror while fetching metadata with correlation id 2 : {test=3DUNKNOWN_TOPIC_O=
R_PARTITION}
Why the unsecure port can not be connected after config sasl authorization?


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)