Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of mor.yuki@gmail.com designates
 209.85.210.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALqbeQZrKDtxVHNqK+eX17=giJ59S216tzh-rW12QXHf5UNpgw@mail.gmail.com>
References: 
 <CAKc7CJR60xDMGwvKH6jxnFFS8pLY2ns3xEw4rvn+7jECUFKEYg@mail.gmail.com>
	<CALqbeQZrKDtxVHNqK+eX17=giJ59S216tzh-rW12QXHf5UNpgw@mail.gmail.com>
Date: Tue, 12 Jul 2011 00:21:51 +0900
Message-ID: 
 <CAGM0Up_OY0fjqSOFVT1GVK3pOeDS3Uh4zeYe_ghup54T1+4THw@mail.gmail.com>
Subject: Re: Limit what nodes are writeable
From: Yuki Morishita <mor.yuki@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I never used the feature, but there is the way to control access based
on user name.
Configuring both conf/passwd.properties and conf/access.properties, then
modify cassandra.yaml as follows.

# authentication backend, implementing IAuthenticator; used to identify use=
rs
authenticator: org.apache.cassandra.auth.SimpleAuthenticator

# authorization backend, implementing IAuthority; used to limit
access/provide permissions
authority: org.apache.cassandra.auth.SimpleAuthority

2011/7/11 Maki Watanabe <watanabe.maki@gmail.com>:
> Cassandra has authentication interface, but doesn't have authorization.
> So you need to implement authorization in your application layer.
>
> maki
>
>
> 2011/7/11 David McNelis <dmcnelis@agentisenergy.com>:
>> I've been looking in the documentation and haven't found anything about
>> this... =C2=A0but is there support for making a node =C2=A0read-only?
>> For example, you have a cluster set up in two different data centers / r=
acks
>> / whatever, with your replication strategy set up so that the data is
>> redundant between the two places. =C2=A0In one of the places all of the =
incoming
>> data will be =C2=A0processed and inserted into your cluster. =C2=A0In th=
e other data
>> center you plan to allow people to run analytics, but you want to restri=
ct
>> the permissions so that the people running=C2=A0analytics=C2=A0can conne=
ct to
>> Cassandra in whatever way makes the most sense for them, but you don't w=
ant
>> those people to be able to edit/update data.
>> Is it currently possible to configure your cluster in this manner? =C2=
=A0Or would
>> it only be possible through a third-party solution like wrapping one of =
the
>> access libraries in a way that does not support write operations.
>>
>> --
>> David McNelis
>> Lead Software Engineer
>> Agentis Energy
>> www.agentisenergy.com
>> o: 630.359.6395
>> c: 219.384.5143
>> A Smart Grid technology company focused on helping consumers of energy
>> control an often under-managed resource.
>>
>>
>
>
>
> --
> w3m
>


--=20
Yuki Morishita
=C2=A0t:yukim (http://twitter.com/yukim)