oso
Ory Keto
Our great sponsors
oso | Ory Keto | |
---|---|---|
16 | 35 | |
3,403 | 4,610 | |
1.4% | 2.2% | |
6.7 | 8.5 | |
about 1 month ago | 2 days ago | |
Rust | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
oso
-
Who's hiring developer advocates? (October 2023)
Link to GitHub -->
-
Show HN: ILLA is an Open-source alternative to Retool
Not OP but Authentication is easy, authorization is a cross-cutting concern that often requires custom code. E.g., there are people and teams, both of which can have different kinds of access to something (read/write). Sometimes teams have sub-teams. Do the sub-teams have access to the parent teams' resources and/or vice versa? Also what kind of sharing are you going to support? Do people have to have an account to view stuff shared to them or can you just send a link? There are some efforts to make custom DSLs for describing authorization policies, to avoid cross-cutting code[1].
Computed fields require different treatment at every level of the stack. This isn't inherently hard, but it is an extra feature these low-code/no-code platforms need. Where things get difficult is inn migrations. It's common for a field that is computed at the beginning to become customizable, or for the computation to change. When that happens, what should the value be for old columns? Computed fields also often pull data from multiple other tables, which may require some combination of custom queries and database optimization.
[1] https://github.com/osohq/oso
-
Resource-based authentication
Oso and OpenFGA are two alternatives that implement Zanzibar-style authorisation.
- Oso - batteries-included framework for building authorization in your application.
-
Decoupling Authorization Logic from Code in NodeJS
There's Oso as well
-
Is Datalog a good language for authorization?
Well this was fun to see! I'm the CTO of Oso, where we're building Polar (the second of the links mentioned https://docs.osohq.com/).
I have a few really minor nitpicks, so will try and make up for it by adding to the discussion :)
First of all, it doesn't really make sense to talk about Datalog as a good language for authorization, because much like with Prolog there doesn't really exist a single implementation of it. OPA's language Rego is a datalog variant, and Polar started out as a Prolog variant (although it's not really recognisable as one any more).
And that's an important point because otherwise it would be pretty reasonable to decide that: logic programming is good for authorization => you should go find the most battle-tested language out there and use that. For example, there's SWI Prolog [1] and Scryer Prolog [2] as two of my favourites.
To me, the thing that is mind-blowing about logic programming, is (a) how powerful the paradigm is, and (b) how concisely you can implement a logic programming language. Take miniKanren [3] which is a full-blown logic language in a few hundred lines of code.
In my mind, the original article makes a decent case that logic programming is a good fit for authorization. And just generally I love anyone bringing attention to that :)
But to me, the reason logic programming is such a solid foundation for authorization logic is the pieces you can build on top of it. For Polar, we've added:
- Types! So you can write authorization logic over your data types and help structure your logic. We've implemented this by simply adding an additional operator into the language that can check types
-
Hey Rustaceans! Got an easy question? Ask here (52/2021)!
First time hearing about rhai, but there's a project in that space called Oso that's authored in Rust and uses a different DSL than Rego. You may or may not find it appealing.
-
Hey Rustaceans! Got an easy question? Ask here (44/2021)!
Authentication is probably the aspect of it that's the weakest. Authorization has a few nice libs, with Oso probably being the nicest, but authentication is mostly roll your own from what I've seen.
-
We Built a Cross-Platform Library with Rust
> Hopefully Oso open source their library.
https://github.com/osohq/oso seems to have the core, C FFI, and language bindings.
Thanks! PHP is a highly requested language for us and we've been rolling them out based on demand. You can vote for it if you want here https://github.com/osohq/oso/issues/791
Ory Keto
-
Show HN: Blueprint for a distributed multi-region IAM with Go and CockroachDB
One of Ory’s core competencies is permissions. We built the first Google Zanzibar implementation in the world and it’s part of Ory Network‘s global multi-region platform (https://github.com/ory/keto)
A push model is also valid if you’re heavy on policies and can accept eventual consistency. We will investigate how to generally push things to the edge (like we did with Ory Edge Sessions) or to cryptographic verification wherever staleness is acceptable.
By solving the primitives correctly in the beginning (with a multi region architecture) that job does become a lot easier, which is what we decided doing at Ory :)
-
Show HN: Open-source IAM Ory Kratos v1.0 with Passkeys, MFA and multi-region
slightly off-topic, but related to what ory is doing in general. How do you usually do authorization-aware search?
Imagine, I have a bunch of Google docs and using https://github.com/ory/keto for authorization. I can quickly answer the question "does user X have access to document Y", but it is not easy to do "search all documents with word Hello in it, for which I have access" because access can be granted through nested groups (give read access to everyone in DepartmentA, and I am part of child department)
-
how to design database for Access Control Privileges ?
if you want to integrate an existing framework see if https://github.com/ory/keto solves your problems, there are similiar frameworks that support ABAC
-
Understanding Google Zanzibar and Why Shines at Building Permissions
Shameless plug for Ory Keto, probably the best reference implementation IMO https://github.com/ory/keto
- We built an open source authorization service based on Google Zanzibar
-
Open-source authorization service and policy engine based on Google Zanzibar
Looks cool, wonder how it compares to Keto and Casbin.
-
Launch HN: Warrant (YC S21) – Authorization and access control as a service
How does Warrant compare to other Zanzibar based solutions like Ory Keto ?https://github.com/ory/keto
-
Show HN: Open-source authorization service based on Google-Zanzibar
Interesting to see another project open sourced around Google Zanzibar. On a timeline for context:
- Ory came out first with Ory Keto ( https://github.com/ory/keto ) which is trying to be a close adaptation of the paper. Initially, many concepts were missing but they are making a lot of progress with the DSL and it interfaces with the rest of Ory (OAuth2, User Mangement)
- Authzed came out as a SaaS only, open sorucing the code base later on at https://github.com/authzed/spicedb
- Auth0 has been playing around with Zanzibar concepts in various forms and published a beta service at https://dashboard.fga.dev - apparently now also open source parts of it similar to what Authzed did: https://github.com/openfga
- Permify - who on a side note spammed me quite a lot with outreach because I was active in these communities - joins as well https://github.com/Permify/permify
It's exciting to see so much movement, yet also sad that so many companies are brewing their own beer instead of working collaborative on the more succesful projects. Feels like we'll just end up with one or two successful projects (looking at Ory / Auth0 here) with the rest perishing. I'm wondering if there truly is a business model for just this permission system as a saas service (looks like this is what everyone is going with). Here I'm giving Auth0 probably the biggest plus as they have an established identity service. Then again, Okta (parent of Auth0) and Auth0 themselves are not particularly known for good business practices that we usually expect from developer tooling.
What's refreshing though with Permify is that they are trying a bit of a different approach to Zanzibar!
-
Zanzibar-like authorization framework written in Go
Er, Ory Keto is written in Go.
What are some alternatives?
CASL - CASL is an isomorphic authorization JavaScript library which restricts what resources a given user is allowed to access
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
node-casbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Node.js and Browser
spicedb - Open Source, Google Zanzibar-inspired permissions database to enable fine-grained access control for customer applications
casbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Golang: https://discord.gg/S5UjpzGZjN
django-guardian - Per object permissions for Django
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
django-rules - Awesome Django authorization, without the database
cerbos - Cerbos is the open core, language-agnostic, scalable authorization solution that makes user permissions and authorization simple to implement and manage by writing context-aware access control policies for your application resources.
Ory Kratos - Next-gen identity server replacing your Auth0, Okta, Firebase with hardened security and PassKeys, SMS, OIDC, Social Sign In, MFA, FIDO, TOTP and OTP, WebAuthn, passwordless and much more. Golang, headless, API-first. Available as a worry-free SaaS with the fairest pricing on the market!