Hey Sam,
I agree that Jolokia bypasses the authentication when connecting to JMX. I
talked about it with Jon Haddad in the past. However, there is an option to
specify that we wanna use jaas and I thought it would use the configuration
file like JMX would. That’s probably where I’m wrong but
The built-in Cassandra auth for JMX works at the connector (i.e. RMI) level. If
you try a direct JMX connection, such as jconsole, you should see the Cassandra
access controls being enforced. As I understand it, Jolokia bypasses the
connectors and so this auth config has no effect. In fact,
Hey guys,
I never got any answer from Jolokia ML or on the GitHub project. Is there
anyone who configured it with success ?
—
Cyril Scetbon
> On Dec 16, 2018, at 6:21 AM, Cyril Scetbon wrote:
>
> Hey guys,
>
> I’ve followed
>
Nvm, I’m gonna send that email to the user ML first.
Regards
—
Cyril Scetbon
> On Dec 16, 2018, at 12:21 AM, Cyril Scetbon wrote:
>
> Hey guys,
>
> I’ve followed
> https://docs.datastax.com/en/cassandra/3.0/cassandra/configuration/secureJmxAuthentication.html
> to setup JMX with Cassandra’s
Hey guys,
I’ve followed
https://docs.datastax.com/en/cassandra/3.0/cassandra/configuration/secureJmxAuthentication.html
to setup JMX with Cassandra’s internal auth using Cassandra 3.11.3
However I still can connect to JMX without authenticating. You can see in the
following attempts that
