Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Augment user-to-database permission to CRUD #322

Open
tock-ibm opened this issue Jan 17, 2022 · 0 comments
Open

Augment user-to-database permission to CRUD #322

tock-ibm opened this issue Jan 17, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@tock-ibm
Copy link
Contributor

tock-ibm commented Jan 17, 2022

Right now a user can have either a read or write permission to a database.
In a scenario where records on the DB represent tokens, we want to add more control on who can insert records, and delete records. Inserting would be like minting, deleting like redeeming.

It is proposed to extend the RW flags on the user-to-db mapping to CRUD - create, read, update, delete.

Another option is to add a 5th flag "A" for "Access" to distinguish between users that can change the ACLs and those that cannot. Or maybe this is better done on the ACLs on the key?

In addition we need to review the relation between the database level permissions and key-level permissions and clearly define the rules:

database \ key | Read | ReadWrite | (?) AccessControl
Create ..................... | ? | ? |
Read ......................... | ? | ? |
Update ..................... | ? | ? |
Delete ....................... | ? | ? |
Access ....................... | ? | ? |

@tock-ibm tock-ibm added the enhancement New feature or request label Jan 17, 2022
@tock-ibm tock-ibm added this to the v0.3 milestone Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants