Skip to content
Discussion options

You must be logged in to vote

Hello, Thibaud!

I didn’t design it around any specific "classic pattern", but the idea is close to a Specification-like approach: explicit authorization rules evaluated against a context. For many projects, especially as a starting point, in-process authorization like this can be more than enough. And honestly, I rarely see "pure" RBAC/ReBAC/ABAC in real projects - authorization is usually shaped by business needs.

One can also see a guard-style API, where the action is encoded in the method name - check_can_<do>(context). For fine-grained enterprise authorization, one possible approach is to rely on an external Policy Decision Point (e.g. OPA) - then you add an application port to that P…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by ivan-borovets
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants