Interestingly I don't see the auth tests that are failing in 3.4 failing on
trunk (they pass), instead a number of tests fail with "Address already in
use"
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-java11/3/#showFailuresLink
3.4 is using
<property name="apache-directory-server.version" value="2.0.0-M15"/>
<property name="apache-directory-api.version" value="1.0.0-M20"/>
while trunk moved to kerby, wonder if that could be it (sasl fails at
least)?
<property name="kerby.version" value="1.1.0"/>
Patrick
On Sat, Jul 21, 2018 at 12:02 AM Patrick Hunt <ph...@apache.org> wrote:
> Thanks Enrico. Possible. However afaict Jenkins is running build 19 (build
> 11-ea+19) and I didn't notice anything obvious in the notes for 19+ related
> to sasl/kerb.
>
> Patrick
>
> On Fri, Jul 20, 2018 at 11:48 PM Enrico Olivelli <eolive...@gmail.com>
> wrote:
>
>> In java11 there are a bunch of news about Kerberos, maybe it is related
>>
>> http://jdk.java.net/11/release-notes
>>
>> My 2 cents
>> Enrico
>>
>> Il sab 21 lug 2018, 08:03 Patrick Hunt <ph...@apache.org> ha scritto:
>>
>> > Hey folks, I added a couple Jenkins jobs based on Java 11 which is set
>> to
>> > release in September. Jenkins is running a pre-release
>> >
>> >
>> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch34_java11/
>> >
>> > java version "11-ea" 2018-09-25
>> > Java(TM) SE Runtime Environment 18.9 (build 11-ea+19)
>> > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+19, mixed mode)
>> >
>> >
>> > Anyone have insight into what's failing here?
>> >
>> > 2018-07-20 14:39:27,126 [myid:2] - ERROR
>> > [QuorumConnectionThread-[myid=2]-3:QuorumCnxManager@268] - Exception
>> > while connecting, id: [0, localhost/127.0.0.1:11223], addr: {},
>> > closing learner connection
>> > javax.security.sasl.SaslException: 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 Zookeeper Quorum Member's received SASL token.
>> >
>> > ...
>> >
>> > Entered Krb5Context.initSecContext with state=STATE_NEW
>> > Found ticket for lear...@example.com to go to
>> > krbtgt/example....@example.com expiring on Sat Jul 21 14:39:01 UTC
>> > 2018
>> > Service ticket not found in the subject
>> > 2018-07-20 14:39:27,127 [myid:0] - ERROR
>> > [QuorumConnectionThread-[myid=0]-2:SaslQuorumAuthServer@133] - Failed
>> > to authenticate using SASL
>> >
>> >
>> >
>> >
>> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch34_java11/2/#showFailuresLink
>> >
>> > Patrick
>> >
>> --
>>
>>
>> -- Enrico Olivelli
>>
>
