[
https://issues.apache.org/jira/browse/CASSANDRA-14317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Brown resolved CASSANDRA-14317.
-------------------------------------
Resolution: Won't Fix
Implementing a plug-in model is far beyond the scope of achieving a stable 3.11
at this time. Thus, I'm closing this as CASSANDRA-12151 is now committed.
[~vinaykumarcse] has told me that backporting CASSANDRA-12151 is not an overly
burdensome (yet not completely simple) task. We won't do that for 3.11, but you
might want to try it if you need auditing in 3.11.
> Auditing Plug-in for Cassandra
> ------------------------------
>
> Key: CASSANDRA-14317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14317
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Environment: Cassandra 3.11.x
> Reporter: Anuj Wadehra
> Priority: Major
> Labels: security
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> Cassandra lacks database auditing feature. Till the new feature is
> implemented as part of CASSANDRA-12151, a database auditing plug-in can be
> built. The plug-in can be implemented and plugged into Cassandra by
> customizing components such as Query Handler , Authenticator and Role
> Manager. The Auditing plug-in shall log all CQL queries and user logins.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
