CODEWITHSUNDEEP
architectureauthorizationaccess-controlrbac
D.B.K
D.B.K

Reputation: 429

Too many roles with RBAC. Alternatives?

To represent the fact that role X can do Y on resource Z, I create a role called "role-Y:Z". The problem is, the number of "resource"s here is ever increasing, and so are the roles.

For every resource that I create, I end up creating 4 roles.

Problem is, RBAC is too coarse-grained for my usecase.

Am I implementing RBAC the wrong way? Any idea how to avoid this role explosion? Maybe I should not use RBAC at all?

Upvotes: 2

Views: 1201

Answers (1)

Maria Ines Parnisari
Maria Ines Parnisari

Reputation: 17506

Maybe I should not use RBAC at all?

You need ReBAC (Relationship Based Access Control) :)

ReBAC solutions such as those based on Google's Zanzibar paper are a good solution for your need of fine-grained permissions.

Some of the companies offering Fine Grained Authorization include:

Upvotes: 2

Related Questions