[
https://issues.apache.org/jira/browse/CASSANDRA-12766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562196#comment-15562196
]
Sam Tunnicliffe commented on CASSANDRA-12766:
---------------------------------------------
Just as a reference, CASSANDRA-11695 (which is in review, but currently blocked
on making some minor changes to ccm/dtests) moves the JMX config out of
cassandra-env and into cassandra.yaml. In that patch, the nodetool script
uses a simple grep to read the jmx port, but extracting the jmx ssl config from
the yaml would be trickier.
> Determine SSL for nodetool based on cassandra-env.sh
> ----------------------------------------------------
>
> Key: CASSANDRA-12766
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12766
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Environment: Linux
> Reporter: Simon Fontana Oscarsson
> Priority: Trivial
> Fix For: 3.x
>
> Attachments: Nodetool-read-ssl-argument-from-cassandra-env.patch
>
>
> Instead of specifying SSL with the --ssl flag we could enable SSL always when
> com.sun.management.jmxremote.ssl=true in cassandra-env.sh. A --no-ssl flag
> could be useful when you don't want ssl enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
