Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D39B3200D27 for ; Wed, 11 Oct 2017 01:17:19 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D228F160BE1; Tue, 10 Oct 2017 23:17:19 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 22A06160BE0 for ; Wed, 11 Oct 2017 01:17:18 +0200 (CEST) Received: (qmail 82508 invoked by uid 500); 10 Oct 2017 23:17:18 -0000 Mailing-List: contact user-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@curator.apache.org Delivered-To: mailing list user@curator.apache.org Received: (qmail 82499 invoked by uid 99); 10 Oct 2017 23:17:18 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2017 23:17:18 +0000 Received: from mail-lf0-f44.google.com (mail-lf0-f44.google.com [209.85.215.44]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 3A5F11A0117 for ; Tue, 10 Oct 2017 23:17:16 +0000 (UTC) Received: by mail-lf0-f44.google.com with SMTP id l23so104893lfk.10 for ; Tue, 10 Oct 2017 16:17:15 -0700 (PDT) X-Gm-Message-State: AMCzsaW/4+MdUkYkZwiNFnVTrS39EtPrejy2Gfm8n4HVtoFApZpl2y6+ 8D+4AOx7DQ1z7EuzosATY0pgzWLHQQNxbhVBH2s= X-Google-Smtp-Source: AOwi7QA6U7pe/njldIz88kl3IBkSL0t5rSZT/45sdTuD+mqFjUKX+DOfZwKCaDmRbfGAXNDcrOIJbf1vMhIYnT46zCE= X-Received: by 10.46.84.29 with SMTP id i29mr1410116ljb.87.1507677434184; Tue, 10 Oct 2017 16:17:14 -0700 (PDT) MIME-Version: 1.0 Reply-To: cammckenzie@apache.org Received: by 10.25.151.149 with HTTP; Tue, 10 Oct 2017 16:17:13 -0700 (PDT) In-Reply-To: References: From: Cameron McKenzie Date: Wed, 11 Oct 2017 10:17:13 +1100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Configuring security for TestingCluster? To: user@curator.apache.org Content-Type: multipart/alternative; boundary="f403045fb636e68afa055b39813c" archived-at: Tue, 10 Oct 2017 23:17:20 -0000 --f403045fb636e68afa055b39813c Content-Type: text/plain; charset="UTF-8" I haven't tried it, and I don't think it's done anywhere specifically in the Curator codebase, but given that the TestingCluster and associated classes are just wrappers around the underlying Zookeeper server, I can't see why it couldn't be done. On Wed, Oct 11, 2017 at 8:02 AM, Philip Zampino wrote: > I'm wondering if it's possible to configure any kind of security (i.e., > authentication) to a (curator-test) TestingCluster. > > If so, is it documented anywhere? > > Thanks, > Phil > --f403045fb636e68afa055b39813c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I haven't tried it, and I don't think it's don= e anywhere specifically in the Curator codebase, but given that the Testing= Cluster and associated classes are just wrappers around the underlying Zook= eeper server, I can't see why it couldn't be done.

On Wed, Oct 11, 2017 at 8:0= 2 AM, Philip Zampino <pzampino@gmail.com> wrote:
I= 'm wondering if it's possible to configure any kind of security (i.= e., authentication) to a (curator-test)=C2=A0TestingCluster.

If so, is= it documented anywhere?

Thanks,
= =C2=A0 =C2=A0Phil

--f403045fb636e68afa055b39813c--