incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Reddy <>
Subject Re: Securing Cassandra database
Date Sat, 05 Apr 2014 06:24:38 GMT

If you want to just secure OpsCenter itself take a look here:

If you want to enable internal authentication and still allow OpsCenter
access, you can create an OpsCenter user and once you have auth turned
within the cluster update the cluster config with the user name and
password for the OpsCenter user.

Depending on your installation type you will find the cluster config in one
of the following locations:
Packaged installs: /etc/opscenter/clusters/<cluster_specific>.conf
Binary installs: <install_location>/conf/clusters/<cluster_specific>.conf
Windows installs: Program Files (x86)\DataStax

Open the file and update the username and password values under the
[cassandra] section:

username =
seed_hosts =
api_port =
password =

After changing properties in this file, restart OpsCenter for the changes
to take effect.


On Sat, Apr 5, 2014 at 6:54 AM, Check Peck <> wrote:

> Hi All,
> We would like to secure our Cassandra database. We don't want anybody to
> read/write on our Cassandra database leaving our team members only.
> We are using Cassandra 1.2.9 in Production and we have 36 node Cassandra
> cluster. 12 in each colo as we have three datacenters.
> But we would like to have OPSCENTER working as it is working currently.
> Is this possible to do anyhow? Is there any settings in yaml file which we
> can enforce?
> *Raihan Jamal*

View raw message