authz
warrant
authz | warrant | |
---|---|---|
7 | 39 | |
227 | 990 | |
- | 2.5% | |
5.8 | 8.9 | |
18 days ago | 7 days ago | |
Go | Go | |
MIT License | 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.
authz
- Authorization back end that comes with a front end
- Authorization back end that comes with a UI for RBAC and ABAC
- Authz: A centralized authorization back end with its front end
-
AWS Cognito - Am I doing this right?
There are auth systems like ory.sh and https://github.com/eko/authz and many other open source that are a lot better.
- authz: Authorization backend that comes with a UI for RBAC and ABAC permissions
- Authorization back end that comes with a UI for RBAC and ABAC permissions
- Authz: Authorization back end that comes with a UI for RBAC and ABAC permissions
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?
qbee-agent - Device agent component of the qbee.io IoT device management platform.
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.
policy-enforcer - Represent your rego rules programmatically.
OPAL - Policy and data administration, distribution, and real-time updates on top of Policy Agents (OPA, Cedar, ...)
topaz - Cloud-native authorization for modern applications and APIs
sablier - Start your containers on demand, shut them down automatically when there's no activity. Docker, Docker Swarm Mode and Kubernetes compatible.
casbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Golang: https://discord.gg/S5UjpzGZjN
yai - Your AI powered terminal assistant.
awesome-auth - đ Software and Libraries for Authentication & Authorization & SSO & IAM
whisper - Pass secrets as environment variables to a process [Moved to: https://github.com/busser/murmur]
casbin-server - Casbin as a Service (CaaS)
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.