ogazitt

22 ms·

1. 1.▲
   Building permission-aware AI chatbots(aserto.com)

   1 points by ogazitt 2y ago|0 comments
2. 2.▲
   RAG with Access Control(pinecone.io)

   3 points by ogazitt 2y ago|2 comments
3. 3.▲
   by ogazitt 2y ago

   Congrats on the launch! [Disclosure: I'm one of the co-founders of Aserto, the creators of Topaz]. The problem of data filtering is indeed a huge part of building an effective authorization system. Partial evaluation is one way of doin
4. 4.▲
   by ogazitt 3y ago

   If you want to try Topaz (which supports all three), check it out here [0]. We'd love to help you solve your authorization scenario :) [0] https://github.com/aserto-dev/topaz
5. 5.▲
   by ogazitt 3y ago

   Topaz is essentially a combination of OPA (which is used as the decision engine, with full support for Rego), and a Zanzibar-style directory, which is fairly isomorphic to what OpenFGA has implemented. The advantage is that it's a sing
6. 6.▲
   by ogazitt 3y ago

   OPA is a great tool for implementing a policy-as-code system. But if you're trying to use it for application authorization (e.g. fine-grained authz for B2B SaaS or a set of internal applications), you may find that its policy story is
7. 7.▲
   by ogazitt 3y ago

   LetsGo looks really cool! Excited to see how this evolves.
8. 8.▲
   by ogazitt 3y ago

   Really cool to see an identity provider that's free, both in price and in friction. Nicely done!
9. 9.▲
   by ogazitt 3y ago

   Thanks! Yes, the days where you have to hand-roll authorization logic are (hopefully) soon to be behind us :)
10. 10.▲
    by ogazitt 3y ago

    Thanks! That's exactly the analogy we think of... Auth0 : AuthN :: Topaz : AuthZ :)
11. 11.▲
    by ogazitt 3y ago

    Thanks! Do let us know what your favorite feature is in the 0.30 release :)
12. 12.▲
    by ogazitt 3y ago

    Thanks! ABAC and ReBAC are indeed complementary, and you can build powerful authorization models by combining the best of these.
13. 13.▲
    by ogazitt 3y ago

    Thanks! "topaz test" is already pretty useful, and we hope to bring assertions into the visual console in a future release.
14. 14.▲
    by ogazitt 3y ago

    Thanks for the question! Those are both great projects. Topaz combines the best elements of both: * It uses OPA as its decision engine and Rego as the policy language, and supports the "policy as code" methodology * It also impl
15. 15.▲
    Show HN: Topaz 0.30 – OSS authz service combining the best of OPA and Zanzibar(aserto.com)

    35 points by ogazitt 3y ago|16 comments
16. 16.▲
    It's time for authorization standards: AuthZEN WG at OpenID Foundation(aserto.com)

    11 points by ogazitt 3y ago|2 comments
17. 17.▲
    by ogazitt 3y ago

    Thanks! Analogies are always challenging, but the Zanzibar ReBAC model fits the “opinion” and “simplicity” of REST (at least when compared to SOAP). We will definitely need the “Rails” equivalent for making ReBAC accessible to many more dev
18. 18.▲
    by ogazitt 3y ago

    Good question. OPA is best suited for ABAC-centric scenarios, where your authorization logic is expressed in terms of attributes on users, objects, or environment. The ReBAC / Zanzibar model is more opinionated, but most use-cases seem
19. 19.▲
    OPA : Zanzibar :: SOAP : REST?(aserto.com)

    18 points by ogazitt 3y ago|4 comments
20. 20.▲
    by ogazitt 4y ago

    Thanks! Let us know if you have any feedback!
21. 21.▲
    by ogazitt 4y ago

    Thanks! Would love to exchange ideas. Please feel free to join our community slack [0] or open an issue on the GitHub tracker [1]. We also accept PR's :) [0] https://www.aserto.com/slack [1] https://github.c
22. 22.▲
    by ogazitt 4y ago

    Really great context on what worked and what was perhaps overengineered. The approachability of any system by its consumers (developers in this case) is hugely important. You've done a good job with Oso :)
23. 23.▲
    by ogazitt 4y ago

    Would love any feedback you have on setting up Topaz, if you choose to give it a try! We built it to be useful completely standalone.
24. 24.▲
    by ogazitt 4y ago

    I'm Omri, one of the Aserto co-founders. Very much agree that this space is still pretty early - we all started building developer-centric authorization solutions in the last couple of years, and we're still in the phase where ex
25. 25.▲
    by ogazitt 4y ago

    Our design approach with Aserto has been to have a single OPA-based decision engine integrated with a built-in directory. So Topaz carries this forward. We do have a gRPC contract for the directory (which is pluggable in Topaz), and it woul
26. 26.▲
    by ogazitt 4y ago

    Thanks! :)
27. 27.▲
    by ogazitt 4y ago

    Thanks! We do have Rack middleware [1], as well as a Rails integration [2]. Let us know what you think! [1] https://www.topaz.sh/docs/software-development-kits/ruby/mid... [2] https://www.topaz.sh&
28. 28.▲
    by ogazitt 4y ago

    Two years ago, we founded Aserto to simplify authorization for developers. Authorization is critical and hard to get right, yet isn't a source of differentiation for most applications. Google [1], Airbnb [2], Netflix [3], Carta [4], In
29. 29.▲
    Show HN: Topaz: open-source authorization combining the best of OPA and Zanzibar(github.com)

    132 points by ogazitt 4y ago|32 comments
30. 30.▲
    by ogazitt 4y ago

    That is super cool! Really curious to hear how it's built, how much runs in wasm, how you got (some portions of) postgres to compile to wasm, etc.