[
https://issues.apache.org/jira/browse/CASSANDRA-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040805#comment-14040805
]
Adam Holmberg edited comment on CASSANDRA-7422 at 6/23/14 2:40 PM:
-------------------------------------------------------------------
Thanks for the input. I'm actually just looking for exactly what was stated
above.
My main goal was just to have Cassandra emit this information. Using these logs
a person could answer "who had access to what, when?". It's a basic solution,
and I thought it might be sufficiently generic to be useful to others.
Regarding collection and filtering, we have ancillary services that provide
this -- I'm not sure this is a function Cassandra should provide. I suppose
these events could be collected in Cassandra itself if that is of interest to
anyone.
was (Author: aholmber):
Thanks for the input. I'm actually just looking for exactly what was stated
above.
My main goal was just to have Cassandra emit this information. Using these logs
a person could answer "who had access to what, when?". It's a basic solution,
and I thought it might be sufficiently generic to be useful to others.
Regarding collection and filtering, we have ancillary services that provide
this -- I don't see that as a function Cassandra should provide.
> 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
> Fix For: 1.2.17
>
> 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)
