The Receptionist VS Oso

The Receptionist mentions (0)

Oso mentions (6)

• Solution for ReBAC authz using attributes?

  I know of warrant.dev, osohq.com, and Ory Keto but I don't see that these evaluate based on attributes. Source: over 1 year ago

• Authorization Framework + Data Filtering

  Oso supports applying authorization logic at the ORM layer so that you can efficiently authorize entire data sets. For example, suppose you have millions of posts in a social media application created by thousands of users, and regular users are only authorized to view posts from their friends. It would be inefficient to fetch all of the posts and authorize them one by one. It would be much more efficient to... Source: over 2 years ago

• Node Authorization Framework

  Oso's Node library now provides a configuration-based approach to adding role-based access control (RBAC) to your application. This new library speeds up the time it takes to build fine-grained permissions using roles and related patterns. Here are the docs + quickstart. Source: over 2 years ago

• AuthZ: Carta’s highly scalable permissions system

  > It's crazy this still is part of the stack where there are no great solutions. Seems like a few others have come to the same conclusion :) We're working on this at Oso (https://osohq.com) - I'm the CTO. Oso is an open source framework for authorization. Policies can reference application directly, so any authorization decisions can be made dynamically based on the data. And your data doesn't need to leave your... - Source: Hacker News / almost 3 years ago

• The basics of role-based access control (RBAC) in SQLAlchemy

  To celebrate a new release of Oso, our open-source authorization library, this blog post demonstrates a few ways of modeling role-based access control in Python and SQLAlchemy. It has complex examples to provide you with the building blocks for adding RBAC to your app and are written in a multi-tenant production system. - Source: dev.to / almost 3 years ago