oso 0.27.2

oso is an open source policy engine for authorization that's embedded in your application

Deprecated

We have deprecated the legacy Oso open source library. We have plans for the next open source release and we’re looking forward to getting feedback from the community leading up to that point (please reach out to us in the Slack #help channel). In the meantime, if you’re happy using the Oso open source library now, nothing needs to change – i.e., we are not end-of-lifing (EOL) the library and we’ll continue to provide support and critical bug fixes. More context: here.

Oso

What is Oso?

Oso is a batteries-included framework for building authorization in your application.

With Oso, you can:

• Model: Set up common permissions patterns like role-based access control (RBAC) and relationships using Oso’s built-in primitives. Extend them however you need with Oso’s declarative policy language, Polar.
• Filter: Go beyond yes/no authorization questions. Implement authorization over collections too - e.g., “Show me only the records that Juno can see.”
• Test: Write unit tests over your authorization logic now that you have a single interface for it. Use the Oso debugger or REPL to track down unexpected behavior.

Oso offers libraries for Node.js, Python, Go, Rust, Ruby, and Java.

Our latest creation Oso Cloud makes authorization across services as easy as oso.authorize(user, action, resource). Learn about it.

Documentation

• To get up and running with Oso, try the Getting Started guide.
• Full documentation is available at docs.osohq.com.
• Check out Use Cases to learn more about how teams are using Oso in production.
• To learn about authorization best practices (not specific to Oso), read the Authorization Academy guides.

Community & Support

If you have any questions on Oso or authorization more generally, you can join our engineering team & hundreds of other developers using Oso in our community Slack:

Share your story

We'd love to hear about your use case and experience with Oso. Share your story in our Success Stories issue.

Development

Core

Oso's Rust core is developed against Rust's latest stable release.

Language libraries

Oso's language libraries can be developed without touching the Rust core, but you will still need the Rust stable toolchain installed in order to build the core.

To build the WebAssembly core for the Node.js library, you will need to have wasm-pack installed and available on your system PATH.

Language requirements

To work on a language library, you will need to meet the following version requirements:

• Java: 11+
  • Maven: 3.6+
• Node.js: 12.20.0+
  • Yarn 1.22+
• Python: 3.7+
• Ruby: 2.4+
  • Bundler 2.1.4+
• Rust: 1.46+
• Go: 1.14+

Contributing & Jobs

See: CONTRIBUTING.md.

If you want to work on the Oso codebase full-time, visit our jobs page.

License

See: LICENSE.