News for hackers. Stuff that matters.

Show HN: A No-Code UI for Managing Google-Zanzibar Style ReBAC

Hello HN !

There’s been a lot of discussions [1,2] on how to build ReBAC [3] with Zanzibar and policy-as-code engines, but we (Permit) also think it’s important to talk about the interfaces on top of these implementations. We just launched a No-Code ReBAC interface - would love to know what you think. besides marrying the benefits of Policy as Code and Policy as Graph, the idea here is to create simple enough interfaces that everyone can use, so developers can set the stage and delegate the rest to others. We used Role-derivation as a concept to simplify a lot of the mechanics what should we simplify next (ownership? Groups?) Check out the main page for ReBAC [0] our docs and this healthcare demo-app [4] as well

[0] - https://www.permit.io/rebac [1] - https://news.ycombinator.com/item?id=37165713 [2] - https://news.ycombinator.com/item?id=36504609 [3] - https://www.permit.io/blog/what-is-rebac [4] - https://github.com/permitio/Galactic-Health-Corporation

( 1 comment | 4 points | on HN )
Re:Show HN: A No-Code UI for Managing Google-Zanzibar Style ... by gemanor on Wednesday August 30, 2023 @12:41PM (#37324768)
We started to evaluate ReBAC/Zanzibar lately and also had difficulty considering role derivations or direct user<->resource relationships. Can you please share any thoughts on why you preferred to stick with assignment/derivations and not user<->resource relationship?