oso
django-tenants
Our great sponsors
oso | django-tenants | |
---|---|---|
16 | 9 | |
3,387 | 1,343 | |
0.9% | 1.8% | |
6.7 | 7.9 | |
about 1 month ago | 10 days ago | |
Rust | Python | |
Apache License 2.0 | MIT License |
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.
-
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
django-tenants
- Multitenancy in Django 4.1
-
Multiple sites served via single project question
If you are looking for multitenancy. Django has an awesome package called django-tenants
-
Multi-Tenancy in Django
Some months back i happen to be involved in a multi-tanent based Django project (SaaS), i began my research on multi-tanency and multi-tanancy in django. After researching for some time, i came across the django_tenant library. I studied its documentation and i was able to integrate it into the project i was working on and was able to solve my problem.
- Multiple user logins for one overall "Company Account"
-
How to login user to different schema using django-tenant-schemas?
The problem I am having is I am trying to login a user based on a request's header value to the corresponding tenantin a APIView. I can successfully `authenticate()` the user against a given tenant name, which basically does a `get_or_create` user for that tenant but when I try to use the `django.db` `login()` it gives me this. Think my problem is similar to this GitHub issue https://github.com/django-tenants/django-tenants/issues/245. Has anyone had a similar issue?
-
How to scale a Django App?
I have very good experience with django-tenants: https://github.com/django-tenants/django-tenants
-
How to manage multi tenant in fast-api
Hello, Is there any package similaire to django-tenants for fastapi.
-
Had anyone implemented Tenant registration using django-tenants or django-tenant-schemas ?
this sounds interesting but I have a hard time understanding how this helps in situation. I have succeeded in creating tenants with signals , it's create_tenant_superuser I'm struggling with. And here's the 2 lines of code that command is defined with ...
-
How To Build a Multi-Tenant eCommerce Platform in 3 Months?
Answers to these questions made me choose the django_tenants package.
What are some alternatives?
CASL - CASL is an isomorphic authorization JavaScript library which restricts what resources a given user is allowed to access
django-tenant-schemas - Tenant support for Django using PostgreSQL schemas.
node-casbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Node.js and Browser
Saleor - Saleor Core: the high performance, composable, headless commerce API.
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
django-organizations - :couple: Multi-user accounts for Django projects
django-guardian - Per object permissions for Django
django-multitenant - Python/Django support for distributed multi-tenant databases like Postgres+Citus
django-rules - Awesome Django authorization, without the database
django-pgschemas - Django multi-tenancy through Postgres schemas
Ory Keto - Open Source (Go) implementation of "Zanzibar: Google's Consistent, Global Authorization System". Ships gRPC, REST APIs, newSQL, and an easy and granular permission language. Supports ACL, RBAC, and other access models.
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.