Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: message received from 54.164.171.186
 which is an MX secondary for user@zookeeper.apache.org)
From: Michael Pratt <prattm@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: Cannot delete node after setting ACL
Message-Id: <AF52DCAB-AAF7-4D87-871F-1F73E1923AFA@gmail.com>
Date: Tue, 28 Apr 2015 17:24:51 -0600
References: <37996076ad124635a7081e00a5f239c4@ES07AMSNLNT.srn.sandia.gov>
In-Reply-To: <37996076ad124635a7081e00a5f239c4@ES07AMSNLNT.srn.sandia.gov>
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>

Thanks linda. I mentioned in my post I was able to add/remove nodes when a v=
alid SHA1 hash is provided, but I'm in the same boat of not knowing how to r=
emove it when a bad hash is used. Haven't tried super digest yet, probably t=
he last option before wiping everything.

Thanks,
Mike

> On Apr 28, 2015, at 4:17 PM, Dubbert, Linda S <lcdubbe@sandia.gov> wrote:
>=20
> When you use the setAcl command, you must supply the SHA1 digest of the "u=
ser:password" string , e.g.:
> setAcl  /test2  digest:test:V28q/NynI4JI3Rk54h0r8O5kMug=3D:cdrwa
> (The SHA1 hash is for the string "test:test")
>=20
> However, once you get into this situation, where you cannot authenticate t=
o the proper username to delete, I don't know how to get out of it without r=
esetting the database.
>=20
> -          linda