[mailto:li...@beobal.com] On Behalf Of Sam Tunnicliffe
Sent: Tuesday, August 02, 2016 1:00 PM
To: user@cassandra.apache.org
Subject: Re: Set up authentication on a live production cluster
However, the actual keyspace (system_auth) and tables are not created until the
last node is restarted
>
> However, the actual keyspace (system_auth) and tables are not created
> until the last node is restarted with the parameters changed
Actually, this is not strictly true. On 2.2+ the tables in system_auth are
created up front, regardless of the auth config. Practically you can't go
about
I have done it in production without downtime on apache cassandra by
manipulating the user creation using iptables on first node.
Sent from my iPhone
> On Aug 2, 2016, at 9:11 PM, DuyHai Doan wrote:
>
> Thank you Sean for the excellent and details explanation, a lot of
Thank you Sean for the excellent and details explanation, a lot of people
out there start their Cassandra in production without security and wake up
some days, too late
On Wed, Apr 13, 2016 at 10:54 PM, wrote:
> Do the clients already send the credentials? That is
Do the clients already send the credentials? That is the first thing to address.
Setting up a cluster for authentication (and authorization) requires a restart
with the properties turned on in cassandra.yaml. However, the actual keyspace
(system_auth) and tables are not created until the last