kkajla

7 ms·

1. 31.▲
   by kkajla 5y ago

   Hi HN, the Warrant Self Service Dashboard is a Warrant-hosted permission management page that can be added to any application in a few lines of code and lets customers manage their own role and permission assignments (think Stripe Checkout
2. 32.▲
   Self Service Permission Management for Your Customers with Warrant(warrant.dev)

   8 points by kkajla 5y ago|1 comments
3. 33.▲
   Built-In Role Based Access Control Now Available in Warrant(blog.warrant.dev)

   2 points by kkajla 5y ago|0 comments
4. 34.▲
   by kkajla 5y ago

   I'm glad you got some value from my answer. Happy to help! Thank you! We put a lot of effort into maintaining quality documentation, so I appreciate the compliment! Our pricing is intended to scale with an application. $1 per 1,000 API
5. 35.▲
   Insecure Direct Object Reference and How to Protect Against It(blog.warrant.dev)

   4 points by kkajla 5y ago|0 comments
6. 36.▲
   by kkajla 5y ago

   Which service to use for billing will depend on how you plan to charge your customers (flat monthly rate, usage based, etc.), so it's worth thinking about pricing first and then exploring the options available on the market. Even thoug
7. 37.▲
   Authorization in Multi-Tenant SaaS Apps(docs.warrant.dev)

   5 points by kkajla 5y ago|0 comments
8. 38.▲
   Authorization in 2021(blog.warrant.dev)

   3 points by kkajla 5y ago|0 comments
9. 39.▲
   by kkajla 5y ago

   Thanks for your response! A lot of the issues and solutions you mentioned remind me of my time in past roles. More companies deal with authz related issues than we think, yet there aren't many products available that solve these long-t
10. 40.▲
    Implementing Role Based Access Control in a Web Application(blog.warrant.dev)

    25 points by kkajla 5y ago|2 comments
11. 41.▲
    Building Better Access Control for Single Page Apps(twitter.com)

    3 points by kkajla 5y ago|0 comments
12. 42.▲
    by kkajla 5y ago

    A great introductory read on such an expansive topic. Authz is a long-standing problem without a real standardized solution yet. I think improving everyone's understanding of the core problems that authz presents is a nice first step t
13. 43.▲
    by kkajla 5y ago

    Thanks for the response. I agree! That's exactly what we saw first hand at previous roles. Access control usually starts simple, but quickly evolves in complexity.
14. 44.▲
    by kkajla 5y ago

    Very cool! I wasn't aware of SSE. This could be very useful for our React SDK as well. Thank you for sharing :)
15. 45.▲
    by kkajla 5y ago

    Thanks for the response! It is interesting to see the surge in popularity of Zanzibar. Completely agree that Zanzibar itself isn't too difficult to implement (especially since Google published a paper on it). It does provide great flex
16. 46.▲
    by kkajla 5y ago

    Yes, we plan to have a Ruby SDK soon!
17. 47.▲
    by kkajla 5y ago

    Updates to the API are immediately reflected in subsequent access requests, so new users who sign up in your system would immediately have the appropriate access rules
18. 48.▲
    by kkajla 5y ago

    Keto + Oathkeeper together seem to be similar to what Warrant provides. One of our main focuses is providing great developer experience. We're continuing to build out the tooling around this, so stay tuned!
19. 49.▲
    by kkajla 5y ago

    That’s correct, Warrant would act as your authorization service, where you can store access rules for your system and check against them at runtime to protect access to your application. Roles are a common access control model, but you can
20. 50.▲
    by kkajla 5y ago

    Thanks for the question! A couple of things that we think are killer features of Warrant: - The flexible access control modeling. Implementing a basic RBAC scheme isn't too difficult with a couple extra database tables, but going furth
21. 51.▲
    by kkajla 5y ago

    We’re Aditya and Karan, the co-founders of Warrant ( https://warrant.dev/ ). We build APIs and infrastructure to help developers implement authorization and access control in their apps. Implementing flexible authorization th
22. 52.▲
    by kkajla 5y ago

    Hi HN! I decided to create Warrant because I've dealt with the pain of implementing some form of access control at every company I've worked at. It never gets less painful. While there are some really powerful open source librarie
23. 53.▲
    Warrant: Web Application Authorization as a Service(warrant.dev)

    3 points by kkajla 5y ago|1 comments