Viewing profile — akajla

I think one major difference between the Zanzibar implementations that are out there is support for the 'zookie' consistency token (as mentioned in the original paper). OpenFGA afa…

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. imple…

The article references the F-35A which is the conventional take-off/landing variant whereas the VTOL variant is the F-35B.

We offer this natively within Warrant's authz service: https://docs.warrant.dev/guides/feature-flags/

You can encode capabilities/permissions as scopes in distributed tokens (e.g. OAuth) but this can start to break down if you have very granular, fine-grained permissions (e.g. user…

What we're building at Warrant ( https://warrant.dev/ ) might work for a lot of what you mentioned including APIs to build and manage multi-tenancy, groups, users, orgs/tenants. No…

They might not be the exact same concept but they're definitely related. I'd argue feature flags, authorization, and pricing tiers/entitlements all make up modern 'access control' …

> I want to include role (or other) information directly in the token for the sake of convenience This works up until a certain point. Once you get past simple RBAC to more fine-gr…

The self-service dashboard is scoped only to privileged users (typically account/tenant-specific admins like IT admins) that have a specific permission.

Building and maintaining UIs for RBAC and org management (including self-service, user-facing UIs) isn't trivial. That's why we built it into Warrant. We handle basic authz schemes…

Disclaimer: I'm the founder of an authorization company [1] & previously worked at a large, enterprise/SaaS company so basing my comment on my experiences. Your considerations and …

Thanks! There's a lot to build out on the authz & access control side so that's our focus for now. But we've built Warrant in such a way that it plugs-in with any existing or new a…

We have thought about it but still evaluating. In general, our thought here is that in case we go out of business, customers should be able to continue using the software with acce…

This is all very useful, thanks for your feedback! > 3.) Supporting staging/local dev environments with as little additional dev work would be awesome. You may already accomplish t…

Thanks for the feedback! Hoping my responses will be quoted properly: > I share other folks concern regarding a remote api call for authentication, but I think your Edge Agent solu…

Hear you on this, as mentioned in other comments, we have the edge agent to address performance/reliability concerns and are definitely looking into providing full on-prem/self-hos…