Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of
 gcdcu-cassandra-user@m.gmane.org designates 80.91.229.12 as permitted sender)
To: cassandra-user@incubator.apache.org
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Cassandra access control
Date: Wed, 02 Dec 2009 15:55:16 -0600
Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @
 Cienfuegos
Lines: 37
Message-ID: <87eindhwhn.fsf@lifelogs.com>
References: <87eio6p7pb.fsf@lifelogs.com> <87fx7ul6id.fsf@lifelogs.com>
	<1259708330.19220.59.camel@achilles> <87638pl96u.fsf@lifelogs.com>
	<ff1a07b80912020713n2485e001x6a9df005d905b62f@mail.gmail.com>
	<87ljhljhv2.fsf@lifelogs.com> <1259784893.10676.32.camel@achilles>
	<87zl61i0kn.fsf@lifelogs.com> <1259786109.10676.35.camel@achilles>
	<87r5rdhxsr.fsf@lifelogs.com>
	<e06563880912021332v7c12d332w1e83eb85e68d2b6f@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.50 (gnu/linux)
Cancel-Lock: sha1:XiUQ6V4LrqDezx0Fy8VbsnHKqNk=
Sender: news <news@ger.gmane.org>

On Wed, 2 Dec 2009 15:32:35 -0600 Jonathan Ellis <jbellis@gmail.com> wrote: 

JE> 2009/12/2 Ted Zlatanov <tzz@lifelogs.com>:
>> I'd still rather pass something back. �As I said, it allows backends to
>> maintain state when it makes sense to do so and can alleviate the
>> problem of redundant auth queries in the future.

JE> That makes no sense whatsoever.  Backends can maintain state or not
JE> either way; adding a token you have to pass back makes just adds an
JE> extra layer of mapping token -> real state in the simple case of
JE> token-is-only-valid-per-connection and an unreasonable amount of
JE> complexity if you try to make it valid across more than one.

JE> I'm -1 in the apache veto sense on the token idea.

On Wed, 02 Dec 2009 15:38:14 -0600 Eric Evans <eevans@rackspace.com> wrote: 

EE> If not for SSO via shared-state between nodes, then for what? Can you
EE> give a tangible example of "when it makes sense to do so"? Are you sure
EE> this isn't YAGNI? 

Across nodes, backends can't maintain state easily, and even across
threads it's not trivial.  My version allows a distrubuted application
to authenticate once and then reuse the same AuthenticationRequest, as
long as the authentication backends have a permanent token store inside
or outside Cassandra.  If we're going to make the keyspace choice sticky
per connection, we should allow for a way to open multiple connections
to multiple keyspaces without necessarily hitting auth services every
time.

You claim the complexity is unreasonable.  I disagree.  If any
complexity emerges, it will be in the backend code which a particular
organization may need and will write.  For Cassandra itself this is not
an issue and the default case (AllowAll) will not create any such
complexity.

Ted