Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 7 Dec 2016 16:36:58 +0000 (UTC)
From: "Boris Melamed (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13016179.1477666568000.462205.1481128618488@Atlassian.JIRA>
In-Reply-To: <JIRA.13016179.1477666568000@Atlassian.JIRA>
References: <JIRA.13016179.1477666568000@Atlassian.JIRA> <JIRA.13016179.1477666568550@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-12859) Column-level permissions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 07 Dec 2016 16:37:00 -0000


    [ https://issues.apache.org/jira/browse/CASSANDRA-12859?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D15729145#comment-15729145 ]=20

Boris Melamed edited comment on CASSANDRA-12859 at 12/7/16 4:36 PM:
--------------------------------------------------------------------

Please review, the commits are:=20
On my C* trunk fork: https://github.com/bmel/cassandra/commit/4a584dac44e15=
bff6757121bb39bd9c59e8d5131
On my dtest fork: https://github.com/bmel/cassandra-dtest/commit/360b446300=
70481afb1ef1bd4623700f446782eb
These are on feature branches, named 'col-perms-12859' in both projects.

I thought to only create pull requests after an initial review.=20
Let me know if you'd like me to create pull requests already - in which cas=
e I'll also pull the trunk/master changes from the past month, into my bran=
ch...


was (Author: bmel):
Please review, the commits are:=20
On my C* trunk fork: https://github.com/bmel/cassandra/commit/4a584dac44e15=
bff6757121bb39bd9c59e8d5131
On my dtest fork: https://github.com/bmel/cassandra-dtest/commit/360b446300=
70481afb1ef1bd4623700f446782eb
These are on feature branches, named 'col-perms-12859' in both projects.

I thought to only create pull requests after an initial review.=20
Let me know if you'd like me to create pull requests already.

> Column-level permissions
> ------------------------
>
>                 Key: CASSANDRA-12859
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1285=
9
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core, CQL
>            Reporter: Boris Melamed
>              Labels: doc-impacting
>         Attachments: Cassandra Proposal - Column-level permissions v2.doc=
x, Cassandra Proposal - Column-level permissions.docx
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> h4. Here is a draft of:=20
> Cassandra Proposal - Column-level permissions.docx (attached)
> h4. Quoting the 'Overview' section:
> The purpose of this proposal is to add column-level (field-level) permiss=
ions to Cassandra. It is my intent to soon start implementing this feature =
in a fork, and to submit a pull request once it=E2=80=99s ready.
> h4. Motivation
> Cassandra already supports permissions on keyspace and table (column fami=
ly) level. Sources:
> * http://www.datastax.com/dev/blog/role-based-access-control-in-cassandra
> * https://cassandra.apache.org/doc/latest/cql/security.html#data-control
> At IBM, we have use cases in the area of big data analytics where column-=
level access permissions are also a requirement. All industry RDBMS product=
s are supporting this level of permission control, and regulators are expec=
ting it from all data-based systems.
> h4. Main day-one requirements
> # Extend CQL (Cassandra Query Language) to be able to optionally specify =
a list of individual columns, in the {{GRANT}} statement. The relevant perm=
ission types are: {{MODIFY}} (for {{UPDATE}} and {{INSERT}}) and {{SELECT}}=
.
> # Persist the optional information in the appropriate system table =E2=80=
=98system_auth.role_permissions=E2=80=99.
> # Enforce the column access restrictions during execution. Details:
> #* Should fit with the existing permission propagation down a role chain.
> #* Proposed message format when a user=E2=80=99s roles give access to the=
 queried table but not to all of the selected, inserted, or updated columns=
:
>   "User %s has no %s permission on column %s of table %s"
> #* Error will report only the first checked column.=20
> Nice to have: list all inaccessible columns.
> #* Error code is the same as for table access denial: 2100.
> h4. Additional day-one requirements
> # Reflect the column-level permissions in statements of type=20
> {{LIST ALL PERMISSIONS OF someuser;}}
> # When columns are dropped or renamed, trigger purging or adapting of the=
ir permissions
> # Performance should not degrade in any significant way.
> # Backwards compatibility
> #* Permission enforcement for DBs created before the upgrade should conti=
nue to work with the same behavior after upgrading to a version that allows=
 column-level permissions.
> #* Previous CQL syntax will remain valid, and have the same effect as bef=
ore.
> h4. Documentation
> * https://cassandra.apache.org/doc/latest/cql/security.html#grammar-token=
-permission
> * Feedback request: any others?


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