[
https://issues.apache.org/jira/browse/CASSANDRA-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michał Michalski reassigned CASSANDRA-5080:
-------------------------------------------
Assignee: Michał Michalski
> cassandra-cli doesn't support JMX authentication.
> -------------------------------------------------
>
> Key: CASSANDRA-5080
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5080
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.1.6, 1.1.7
> Reporter: Sergey Olefir
> Assignee: Michał Michalski
>
> 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.:
> {quote}
> 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)
> {quote}
> help connect; and cassandra-cli --help do not seem to indicate that there's
> any way to specify JMX login information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
