You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Podkowinski (JIRA)" <ji...@apache.org> on 2017/08/03 11:00:02 UTC

[jira] [Updated] (CASSANDRA-13371) Remove legacy auth tables support

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

Stefan Podkowinski updated CASSANDRA-13371:
-------------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 4.x)
                   4.0
           Status: Resolved  (was: Ready to Commit)

Committed as d74ed4b78886c to 3.0. Merged to 3.11 and trunk.

> Remove legacy auth tables support
> ---------------------------------
>
>                 Key: CASSANDRA-13371
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13371
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Auth
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>              Labels: security
>             Fix For: 4.0
>
>
> Starting with Cassandra 3.0, we include support for converting pre CASSANDRA-7653 user tables, until they will be dropped by the operator. Converting e.g. permissions happens by simply copying all of them from {{permissions}} -> {{role_permissions}}, until the {{permissions}} table has been dropped.
> Upgrading to 4.0 will only be possible from 3.0 upwards, so I think it's safe to assume that the new permissions table has already been populated, whether the old table was dropped or not. Therefor I'd suggest to just get rid of the legacy support.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org