access-controller VS openfga

This is very cool! Do you have any comparison with other Zanzibar OSS projects like https://github.com/ory/keto or https://github.com/authorizer-tech/access-controller ?

I've been working on a scalable open-source version of Google Zanzibar called the Authorizer platform. The implementation varies from that of Authzed by horizontally scaling the query space across more than one node. It uses consistent hashing with bounded loads to assign a specific node to serve the queries for the objects that it's responsible for. It also supports the namespace rewrite specification of the paper and the continuous namespace config monitoring. Much more progress is coming as well!

Take a look, I'd love feedback and to build it into something generally very valuable for the community!

https://github.com/authorizer-tech/access-controller

This feels very much like OpenFGA[0]. I've been evaluating authorization tool for one of my side projects and honestly most tools feels like creating relationships in a graph-like database and querying to see if there is/isn't relationship between two entities. Is there more to this (besides the implementation details) or am I missing something from these tools?

[0] https://openfga.dev/

OpenFGA

OpenFGA is CNCF Sandbox authorization service inspired by Google Zanzibar

- https://authzed.com/spicedb/ - https://cerbos.dev/ - https://openfga.dev/ - https://www.permify.co/

Thanks for the answer. I played around with Keycloak for a bit and I saw that roles could be mapped as token claims, however for systems where you need fine grained access control (where roles are not enough) you need some other solution. One option could be to use an external authorization system. One such system could be OpenFGA https://openfga.dev/ that is based on Google Zanzibar https://research.google/pubs/pub48190/ research paper. This answer on SO is also helpful https://stackoverflow.com/a/75047064/10781180

OpenFGA is similar to Permify https://github.com/openfga/openfga