Articles about authorization, and other news from Oso's engineering team
A new set of reference material to help users take Oso into prod
Ashwyn Nair, Senior Software Engineer at Sensat, dives into how Oso has helped them create a safe space for their users to have full control over who can access their data.
.avif)
Generate TypeScript types from your Polar policy - and much more!
Polar now has its own language server implementation, making it easier to write your authentication policies
Peadar Coyle, Founder at AudioStack, dives into how they went from a homegrown authorization framework to using Oso and why it was critical to make this change for a GenAi company where protecting data is mission critical.
Why we moved from Fargate to ECS on EC2, and how we preserved a zero-downtime architecture in the process.
Announcing a new feature in authorization policies: a limited form of negation (not syntax).
How Oso uses Kafka and an Event Sourcing Architecture to deploy a highly-available, low-latency managed authorization service.
Adding access control to LLM chatbot responses with Oso Cloud and Postgresql
A comprehensive look at the design of Polar, and how we enabled it to operate over distributed data.
.png)
Using local data to answer authorization questions with Oso Cloud
A sample app that demonstrates RBAC, ReBAC, and ABAC in Node.js with Oso Cloud
This post provides specifics on when to use Oso, and when not to.
Simon Robb, Co-founder/CTO at Packsmith, covers the pain of custom-building authorization and the value of a centralized solution.
The 10 types of authorization and how to identify them.
How do you reliably perform authorization in a backend built with microservices? There are lots of valid answers, but they tend to fall into three groups.
Everyone’s talking about Zanzibar, and it’s easy to understand why. It handles authorization for Google, so surely it can handle it for you and me. But at what cost? And does that mean that it’s the right solution for the rest of us?
Tyson Hoffman, Senior Software Engineer at Lumio shares how authorization started as a low priority for their application and how it’s evolved since then. They can now easily define permissions and help curb unintended access.
.png)
Relationship-based access control (ReBAC) is an authorization pattern where permissions are derived from relationships between resources. In this blog post, you will learn how to implement ReBAC in Node.js with Oso Cloud
A guide on how to POC authorization as a service products and a framework for running the evaluation process.
How do you know if buying authorization as a service is right for you?
Adam Lee, Lead Software Engineer at Chief, dives into authorizing data access patterns in their microservices architecture at Chief.
.png)
Introduction to Local Policy Testing with Oso Cloud
.png)
Reasons for migrating to Oso's authorization as a service platform including migrating from monolith to microservices, and centralizing and standardizing authorization.
