Create, Read, Update, and Delete (CRUD) Permissions Mapped to Roles

Securing applications
1

Hi,

There was a thread on CRUD that I followed from here into GitHub, but it is not clear to me what code was checked in to address the issue and how far the code goes to allow for CRUD throughout the application. For example, it is not clear to me whether KeyCloak can support the following scenarios:

  • A role can view a document but not update, delete, or create documents.
  • Another role can read, create, and update documents but not delete them.
  • Yet another role can read, update, create, and delete documents.

The same logic could potentially be applied to other objects within an application such as different classes of assets and users.

Can KeyCloak support these scenarios?

Thanks in advance for your feedback.