You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2022. It is now read-only.
For safety reasons, I think it makes sense to define a few different roles for Cassandra use. A few examples are:
Select from sensor data only role. This could be used by services which only need to present the data.
Select from all tables. This could be used by services which need to export all tables for backups.
Select / insert into sensor data tables. This could be used for ETL services.
Admin. The name says it all.
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.
The text was updated successfully, but these errors were encountered:
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...)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: