You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Fournier, Camille F. [Tech]" <Ca...@gs.com> on 2010/08/19 18:34:38 UTC

handling auth failure in java client

Hi all,

I filed this ticket last week:
https://issues.apache.org/jira/browse/ZOOKEEPER-844

Currently, the Java client ignores auth failures which is extremely problematic for the deployment I am preparing. I have written a patch to correct the problem by adding an AuthFailed KeeperState and checking the auth responses for the AUTHFAILED error code (patch is now attached to the ticket). I checked the flow vs the c client and it seems to basically match. Is there anything I should be aware of beyond this simple fix? All the testing I've done seems fine.

Thanks,
Camille



Re: handling auth failure in java client

Posted by Patrick Hunt <ph...@apache.org>.
Hi Camille, thanks for the submission! I've marked the jira as "patch
available" (by clicking the "submit" link), someone will take a look 
(review). I see that you wrote a test as well, which is great.

Thanks,

Patrick

On 08/19/2010 09:34 AM, Fournier, Camille F. [Tech] wrote:
> Hi all,
>
> I filed this ticket last week:
> https://issues.apache.org/jira/browse/ZOOKEEPER-844
>
> Currently, the Java client ignores auth failures which is extremely
> problematic for the deployment I am preparing. I have written a patch
> to correct the problem by adding an AuthFailed KeeperState and
> checking the auth responses for the AUTHFAILED error code (patch is
> now attached to the ticket). I checked the flow vs the c client and
> it seems to basically match. Is there anything I should be aware of
> beyond this simple fix? All the testing I've done seems fine.
>
> Thanks, Camille
>
>
>