What is the difference between DSE and JMX authentication & authorization . Where to use JMX and where to use DSE . What are the way to choose authentication and authorization between DSE & JMX .
What is the difference between DSE and JMX authentication & authorization . Where to use JMX and where to use DSE . What are the way to choose authentication and authorization between DSE & JMX .
Java Management Extensions (JMX) is a framework that enables tools for managing and monitoring applications through Managed Bean (MBeans) objects.
You can retrieve metrics about a Cassandra cluster via JMX as well as perform actions on the cluster (for example, set compaction throughput). In fact, nodetool
commands query the nodes via JMX on port 7199
.
When you enable JMX authentication, you are securing access to the cluster so only authenticated administrators can query cluster metadata or perform actions on nodes.
Previously, JMX authentication could only be configured with password and access files. Since DSE 5.1, DSE Advanced Security provided support for JMX authentication integrated with DSE Unified Authentication so both LDAP and Cassandra internal authentication is now possible. Cheers!
5 People are following this question.
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2023 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use