RE: Set up authentication on a live production cluster

2016-08-02 Thread SEAN_R_DURITY
[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

Re: Set up authentication on a live production cluster

2016-08-02 Thread Sam Tunnicliffe
> > 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

Re: Set up authentication on a live production cluster

2016-08-02 Thread Jai
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

Re: Set up authentication on a live production cluster

2016-08-02 Thread DuyHai Doan
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

RE: Set up authentication on a live production cluster

2016-04-13 Thread SEAN_R_DURITY
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