neupatr

3 ms·

1. 1.▲
   by neupatr 5y ago

   So the idea in the paper is that you store a version token (aka. zookie) next to every object version. When you ask Zanzibar if a user is allowed to modify it, the request contains the stored token. Then you get a new token with a successfu
2. 2.▲
   by neupatr 5y ago

   Exactly, all of our products come without any UI whatsoever. There are example UIs that could be improved, but they can get you started easily. Something like stripe's hosted pages is on our list, just not had the time to implement it
3. 3.▲
   by neupatr 5y ago

   We see it as a very universal service, so integration with k8s is definitely on our list, but there are no concrete plans yet. The ACLs are just so generic, you can describe anything with it.
4. 4.▲
   by neupatr 5y ago

   OPA takes a whole different approach. They basically have a specific language and a corresponding interpreter. The previous version of Keto was based off of OPA. We discovered that it is not suitable for our needs and what we want to offer
5. 5.▲
   by neupatr 5y ago

   Keto only does authorization, independent of users, devices, bots, applications, ... Basically you store your ACLs there and then ask "is _subject_ allowed to do _relation_ on _object_". All the variables are whatever you define t
6. 6.▲
   by neupatr 5y ago

   Thank you ;)
7. 7.▲
   by neupatr 5y ago

   Hm good point. The project itself exists already for quite some time now, this is just a complete rewrite. It is named after an ancient Greek goddess: https://en.wikipedia.org/wiki/Ceto (all of our projects are named a
8. 8.▲
   by neupatr 5y ago

   Hello! I am one of the maintainers of Ory Keto. We spent a lot of time and effort to read, learn, and analyse the Google Zanzibar paper ( https://research.google/pubs/pub48190/ ) and the release brings that all toge