|
|
|
|
|
|
by alex-olivier
1218 days ago
|
|
|
(Disclaimer: I work for Cerbos[1]) When we started working on Cerbos[1] the very first external bit of tooling we released was the Cerbos Playground[2] which does exactly what you say - allows you to see the requests and responses as they make changes to their policies, making it easier to test and refine their rules. This is a great starting point to prototype and test whether a decoupled authorization system is right for your use case. Cerbos uses YAML rather than a custom DSL to try and address the fact that authorization requirements generally don't sit with developers, rather a product owner of some sorts who is going to want to be able to comprehend the logic behind the permissions model. [1] https://cerbos.dev
[2] https://play.cerbos.dev |
|
|