If by Permission class you are referring to the enum class which holds the different permissions. Then that’s one possible solution. The other would be expanding the existing permission class. We then use the internal authorizer in Cassandra to authorize against. We would need a way to create permissions via CQL and create a new type of resource which represents a JMX resource.
-----Original Message----- From: Jonathan Ellis [mailto:jbel...@gmail.com] Sent: August 17, 2015 6:00 PM To: dev Subject: Re: Should we align JMX Authentication with internal Cassandra authentication? So we would create a new permission class for JMX? On Mon, Aug 17, 2015 at 8:34 AM, Jan Karlsson <jan.karls...@ericsson.com> wrote: > Hello fellow devs, > > Currently JMX authentication is handled by using a password file. I > was thinking we could make this a little more sophisticated. > What I propose is, we plug JMX so that it uses the internal > authenticator Cassandra has to authenticate the user. This will allow > us to authenticate towards the Cassandra database. (No pesky password > file) We can make this pluggable so that users could add their own > authenticator and authorizer. > > I have created a JIRA ticket on this as I have been working on a > solution which would let us do precisely this. > https://issues.apache.org/jira/browse/CASSANDRA-10091 > > What are your thoughts on this? > > Best Regards > Jan Karlsson > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
