cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10091) Integrated JMX authn & authz
Date Thu, 28 Apr 2016 12:11:13 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262040#comment-15262040
] 

Robert Stupp commented on CASSANDRA-10091:
------------------------------------------

True, auth does not work while the node hasn't joined. But it feels uncomfortable to disallow
JMX access in that phase.

Could we apply a restricted policy while the node has not joined and allow unauthenticated
access during that phase? A policy that only allows reads ({{Permission.SELECT}}+{{Permission.DESCRIBE}})
plus {{Permission.EXECUTE}} on the necessary methods.

Maybe also restricted to connections from {{localhost}} (feels doable by wrapping the server-socket
created by {{SslRMIServerSocketFactory#createServerSocket}} and check the {{Socket}}'s remote
addr returned by {{ServerSocket.accept}} - or put it into a {{ThreadLocal}} and check it in
{{CassandraLoginModule.authenticate}}).

> Integrated JMX authn & authz
> ----------------------------
>
>                 Key: CASSANDRA-10091
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10091
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jan Karlsson
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 3.x
>
>
> It would be useful to authenticate with JMX through Cassandra's internal authentication.
This would reduce the overhead of keeping passwords in files on the machine and would consolidate
passwords to one location. It would also allow the possibility to handle JMX permissions in
Cassandra.
> It could be done by creating our own JMX server and setting custom classes for the authenticator
and authorizer. We could then add some parameters where the user could specify what authenticator
and authorizer to use in case they want to make their own.
> This could also be done by creating a premain method which creates a jmx server. This
would give us the feature without changing the Cassandra code itself. However I believe this
would be a good feature to have in Cassandra.
> I am currently working on a solution which creates a JMX server and uses a custom authenticator
and authorizer. It is currently build as a premain, however it would be great if we could
put this in Cassandra instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message