[ 
https://issues.apache.org/jira/browse/CASSANDRA-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko resolved CASSANDRA-7422.
------------------------------------------

       Resolution: Not a Problem
    Fix Version/s:     (was: 1.2.19)

Closing as Not a Problem, for now. If we decide to do it, eventually, I'd 
rather we went for a more complete comprehensive audit log solution.

In the meantime, you can subclass CassandraAuthorizer and wrap its methods with 
logging calls, as a reasonable clean solution.

> Logging for Authentication and Authorization
> --------------------------------------------
>
>                 Key: CASSANDRA-7422
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7422
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Adam Holmberg
>            Priority: Trivial
>         Attachments: auth_logging_remote_host.patch.201406666201020
>
>
> We would like to enable Cassandra to log authentication and authorization 
> change events. 
> This facilitates audits on access to certain data. As a side effect it would 
> also make it easier to notice ill-behaved clients connecting repeatedly.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to