[jira] [Closed] (JAMES-3061) Determine the minimum set of permissions for a Cassandra user

["Benoit Tellier (Jira)" <se...@james.apache.org>]

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

Benoit Tellier closed JAMES-3061.
---------------------------------
    Fix Version/s: 3.5.0
       Resolution: Fixed

https://github.com/linagora/james-project/pull/3131 did port our test suite to use a cassandra non priviledged user, with the same rights than what had been documented, in order to prevent us from regressions.

> Determine the minimum set of permissions for a Cassandra user
> -------------------------------------------------------------
>
>                 Key: JAMES-3061
>                 URL: https://issues.apache.org/jira/browse/JAMES-3061
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: René Cordier
>            Priority: Major
>             Fix For: 3.5.0
>
>
> Currently, James relies on a superuser account to connect to Cassandra.  
> This is not adapted for production setups. Eventually, we may have a Cassandra cluster being used by several James instances, all focused on different clients (i.e. these James instances do not belong to the same James "cluster").
> It would be better to have a restricted account to Cassandra.  
> In particular, James should not be able to delete or create a keyspace. In fact, it should only have permissions on its own keyspace. What would be the minimal but sufficient permissions for James to work with such an account? And what would be the command to type in to create such an account from an administrator's point of view?
> *DOD*: apache website documentation for that



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org