[CASSANDRA-5080] cassandra-cli doesn't support JMX authentication.

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.1.11, 1.2.2
• Component/s: Legacy/Tools
• Severity: Normal
• Assignee: Michał Michalski
• Reporter: Sergey Olefir

Authors

Michał Michalski

Reviewers

Aleksey Yeschenko

• Created: 20/Dec/12 11:17
• Updated: 16/Apr/19 09:32
• Resolved: 15/Feb/13 19:55

Description

It seems that cassandra-cli doesn't support JMX user authentication.

Specifically I went about securing our Cassandra cluster slightly – I've added cassandra-level authentication (which cassandra-cli does support), but then I discovered that nodetool is still completely unprotected. So I went ahead and secured JMX (via -Dcom.sun.management.jmxremote.password.file and -Dcom.sun.management.jmxremote.access.file). Nodetool supports JMX authentication via -u and -pw options.

However it seems that cassandra-cli doesn't support JMX authentication, e.g.:

apache-cassandra-1.1.6\bin>cassandra-cli -h hostname -u experiment -pw password
Starting Cassandra Client
Connected to: "db" on hostname/9160
Welcome to Cassandra CLI version 1.1.6

[experiment@unknown] show keyspaces;
WARNING: Could not connect to the JMX on hostname:7199, information won't be shown.

Keyspace: system:
Replication Strategy: org.apache.cassandra.locator.LocalStrategy
Durable Writes: true
Options: [replication_factor:1]
... (rest of keyspace output snipped)

help connect; and cassandra-cli --help do not seem to indicate that there's any way to specify JMX login information.