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 .
DataStax Academy FAQ
DataStax Academy migrated to a new learning management system (LMS) in July 2020. We are also moving to a new Cassandra Certification process so there are changes to exam bookings, voucher system and issuing of certificates.
Check out the Academy FAQ pages for answers to your questions:
- Haven't heard back about exams or vouchers? [NEW August 7]
- When can I book an exam? [NEW August 10]
- How do I qualify for an exam voucher? [NEW August 10]
- How long are the coupons valid for? [NEW August 10]
- Why can't I see my old exam result or certificate? [UPDATED August 10]
- What happened to my previous exam voucher? [UPDATED August 10]
- Why is my previous course progress not shown on the new Academy?
What is the difference between DSE and JMX authentication & authorization?
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.
