Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 29 Aug 2014 13:52:53 +0000 (UTC)
From: "Adam Holmberg (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12722801.1403278547226.2149.1409320373874@arcas>
In-Reply-To: <JIRA.12722801.1403278547226@arcas>
References: <JIRA.12722801.1403278547226@arcas>
Subject: [jira] [Commented] (CASSANDRA-7422) Logging for Authentication and
 Authorization
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Adam Holmberg commented on CASSANDRA-7422:
------------------------------------------

For the record, wrapping didn't really accomplish what they were after because there was no way to get at the client IP from that context. That was the entire point of the patch -- to get the client state over to the auth context so it could be logged.

I'm not going to hound it anymore since I'm not with the company asking for this.

> 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)