Open seanshahkarami opened 6 years ago
I learned how to configure authentication and authorization in Cassandra this evening. I'd like to try to get that in the next revision to allow for very tight control over which processes are allowed to access what parts of the database. (No more risky table drops, inserts, deletes, etc...)
For safety reasons, I think it makes sense to define a few different roles for Cassandra use. A few examples are:
These could help limit the damage that could be done if a service was compromised or improperly designed. This could also help prepare us for a design where the database is easily provisioned into different production, development and testing keyspaces.