You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2018/08/25 07:24:00 UTC
[jira] [Updated] (KAFKA-7338) Fix SASL Kerberos tests with Java 11
[ https://issues.apache.org/jira/browse/KAFKA-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismael Juma updated KAFKA-7338:
-------------------------------
Description:
An example of a failing test is SaslSslAdminClientIntegrationTest:
{code}
[2018-08-25 00:21:31,172] ERROR [Controller id=0, targetBrokerId=0] Connection to node 0 failed authentication due to: An error: (java.security.PrivilegedActionException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Message stream modified (41) - Message stream modified)]) occurred when evaluating SASL token received from the Kafka Broker. Kafka Client will go to AUTHENTICATION_FAILED state. (org.apache.kafka.clients.NetworkClient:663)
{code}
> Fix SASL Kerberos tests with Java 11
> ------------------------------------
>
> Key: KAFKA-7338
> URL: https://issues.apache.org/jira/browse/KAFKA-7338
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Ismael Juma
> Priority: Major
> Fix For: 2.1.0
>
>
> An example of a failing test is SaslSslAdminClientIntegrationTest:
> {code}
> [2018-08-25 00:21:31,172] ERROR [Controller id=0, targetBrokerId=0] Connection to node 0 failed authentication due to: An error: (java.security.PrivilegedActionException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Message stream modified (41) - Message stream modified)]) occurred when evaluating SASL token received from the Kafka Broker. Kafka Client will go to AUTHENTICATION_FAILED state. (org.apache.kafka.clients.NetworkClient:663)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)