cerbos
warrant
Our great sponsors
cerbos | warrant | |
---|---|---|
41 | 39 | |
2,512 | 979 | |
9.6% | 3.4% | |
9.6 | 8.9 | |
5 days ago | 8 days ago | |
Go | 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.
cerbos
- Open Policy Agent
-
Nuxt authorization: How to implement fine-grained access control
In this tutorial you will learn how to use Cerbos to add fine-grained access control to any Nuxt web application, simplifying authorization as a result.
-
šļøāļø Innovate Like Da Vinci: Blending Art and Science in Software Development
In my work with Cerbos, I apply the lessons learned from Da Vinci to tackle authorization challenges. Our approach is to create solutions where functionality seamlessly integrates with developer experience. Constantly iterating and viewing the tools through the users' lens, helps ensure that our access control solutions are robust and dev-friendly.
-
Get started with Cerbos Hub
You may already know of our open source solution - Cerbos Policy Decision Point (PDP); a devtool which helps developers enforce access control over different parts of their software. If you need to learn more about Cerbos in general, we strongly recommend checking out the website and the docs.
- š» 7 Open-Source DevTools That Save Time You Didn't Know to Exist āš
-
Cerbos v0.32 released!
GitHub: https://github.com/cerbos/cerbos URL: https://cerbos.dev
-
Feedback needed: Cerbos Hub is now in public beta
Cerbos Hub is a managed service offering for the open source authorization product, Cerbos.
-
Feedback needed: Cerbos Hub is now in public beta!
Hello fellow devs! I'm with Cerbos (https://cerbos.dev/), a tool designed to manage who can do what in your software applications.
-
š„š Top 10 Open-Source Must-Have Tools for Crafting Your Own Chatbot š¤š¬
Check the quickstart or play with Cerbos in your browser. Support Cerbos on GitHub ā
warrant
-
A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
Warrant ā Hosted enterprise-grade authorization and access control service for your apps. The free tier includes 1 million monthly API requests and 1,000 authz rules.
-
How Open ID Connect Works
The specific challenge with authz in the app layer is that different apps can have different access models with varying complexity, especially the more granular you get (e.g. implementing fine grained access to specific objects/resources - like Google Docs).
Personally, I think a rebac (relationship/graph based) approach works best for apps because permissions in applications are mostly relational and/or hierarchical (levels of groups). There are authz systems out there such as Warrant https://warrant.dev/ (I'm a founder) in which you can define a custom access model as a schema and enforce it in your app.
-
How to Do Authorization - A Decision Framework: Part 1
Let's use warrant.dev as an example. The system provides a set of REST APIs for you to define object types and access policies (called warrants). The general process is first to create object types using HTTP POST:
- Warrant ā open-source Access Control Service
-
A guide to Auth & Access Control in web apps š
https://warrant.dev/ (Provider) Relatively new authZ provider, they have a dashboard where you can manage your rules in a central location and then use them from multiple languages via their SDKs, even on the client to perform UI checks. Rules can also be managed programmatically via SDK.
- Warrant v1.0 - Highly scalable, centralized authorization service based on Google Zanzibar, now v1.0 and production-ready
-
warrant VS openfga - a user suggested alternative
2 projects | 15 Aug 2023
-
Policy as Code vs. Policy as Graph Comparison
I would describe this debate more as Policy-as-Data (Zanzibar) vs Policy-as-Code (OPA et al).
In Zanzibar, all of the information required to make an authorization decision (namespaces, relationship tuples, etc.) is stored in Zanzibar, and the decision engine resolves access checks based on this data. This data can be scaled horizontally (and consistently) as needed for an applicationās needs. This makes Zanzibar a centralized, unified solution for all of an applicationās authorization needs. Iāve found this approach more purpose built / well suited for application authorization.
With OPA and other policy engines, the data required for performing access checks lives somewhere else (maybe the applicationās database) and must be separately queried and included as part of the authorization check because OPA et al. are stateless decision engines. This makes it such that you need to piece together data from different sources in order to get your final decision, which IMO is something most developers donāt want to deal with.
On the flip side, Zanzibarās ānamespacesā are a very simple policy layer not well suited to querying against data outside of Zanzibarās scope (e.g. geolocation, time, etc). For scenarios like this, a full fledged policy-as-code solution is great. However, it should be noted that some open source Zanzibar implementations like Warrant[1] and SpiceDB[2] (mentioned in the article) also offer a policy-as-code layer on top of Zanzibarās graph-based/ReBAC approach to tackle these scenarios.
Disclaimer, Iām one of the founders of Warrant.
[1] https://github.com/warrant-dev/warrant
[2] https://github.com/authzed/spicedb
-
Show HN: Open-Source, Google Zanzibar Inspired Authorization Service
Hey HN, I recently shared my thoughts on why Google Zanzibar is a great solution for implementing authorization[1] and why we decided to build Warrantās core authz service using key concepts from the Zanzibar paper. As I mentioned in the post, we recently open sourced the authz service powering our managed cloud service, Warrant Cloud[2], so I thought Iād share it with everyone here. Cheers!
[1] https://news.ycombinator.com/item?id=36470943
[2] https://warrant.dev/
-
Why Google Zanzibar Shines at Building Authorization
More than two years after choosing to build Warrant atop Zanzibarās core principles, weāre extremely happy with our decision. Doing so gave us a solid technical foundation on which to tackle the various complex authorization challenges companies face today. As we continue to encounter new scenarios and use cases, weāll keep iterating on Warrant to ensure itās the most capable authorization service. To share what we learn and what we build with the developer community, we recently open-sourced the core authorization engine that powers our fully managed authorization platform, Warrant Cloud. If youāre interested in authorization (or Zanzibar), check it out and give it a star!
What are some alternatives?
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
OPAL - Policy and data administration, distribution, and real-time updates on top of Policy Agents (OPA, Cedar, ...)
casbin-server - Casbin as a Service (CaaS)
sablier - Start your containers on demand, shut them down automatically when there's no activity. Docker, Docker Swarm Mode and Kubernetes compatible.
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.
yai - Your AI powered terminal assistant.
oso - Oso is a batteries-included framework for building authorization in your application.
whisper - Pass secrets as environment variables to a process [Moved to: https://github.com/busser/murmur]
opa-envoy-plugin - A plugin to enforce OPA policies with Envoy
Ory Hydra - OpenID Certifiedā¢ OpenID Connect and OAuth Provider written in Go - cloud native, security-first, open source API security for your infrastructure. SDKs for any language. Works with Hardware Security Modules. Compatible with MITREid.
sso-wall-of-shame - A list of vendors that treat single sign-on as a luxury feature, not a core security requirement.
jolt - The social hub for your media server. Rate, review and recommend movies and shows, as well as manage your watchlist, follow friends and more.