Hi HN! Co-Founder of Permit.io here,
I’ve built access-control to my products, thousands of times throughout my career - and at no point did I want to.<p>We adopted OPA, created OPAL.ac (open-source), and Permit.io on top - so no developer would have to build permissions again.<p>To truly solve this problem end-to-end we’re releasing Permit-Elements (<a href="https://permit.io/elements" rel="nofollow">https://permit.io/elements</a>) - embeddable UIs providing the interfaces you need so your end-customers can control access-control (e.g. user-management, audit-logs, approval flows, permission requests, api-key management, …)<p>Check out the full tutorial: <a href="https://youtu.be/xGYdDF65lkQ" rel="nofollow">https://youtu.be/xGYdDF65lkQ</a><p>The solution highlights:
- Authorization for Authorization (who can control who controls permissions)
- Security (auditing, real-time decision making and meeting industry standards)
- An easy integration (generate and embed a JS snippet)<p>There’s a lot more to do, we’d love your feedback on Permit in general, this feature, and others.
Chat with us on Slack (<a href="https://bit.ly/permit-slack" rel="nofollow">https://bit.ly/permit-slack</a>)<p>Thanks,
Or Weis
Guys, you can't do promotional upvoting and commenting on HN. This is in both the site guidelines and the FAQ—that's how important it is:<p><a href="https://news.ycombinator.com/newsguidelines.html" rel="nofollow">https://news.ycombinator.com/newsguidelines.html</a><p><a href="https://news.ycombinator.com/newsfaq.html" rel="nofollow">https://news.ycombinator.com/newsfaq.html</a><p>HN users are extremely vigilant about it and can usually figure out what's going, as they did here, and then they flag the posts and complain to us and use unkind words like 'spam'.
I don't know. This seems to be something I’d get a slap on the hand from our security team. No chance ever they give away the power they have for control who have permission. Just me??
I like where this is headed.<p>A lot of application frameworks have some kind of a security policy engine, but all of these invariably are inadequate - because modern policy management is about interfacing outside of systems, and that they don't do.<p>Exactly in the same way that load balancing should not be a part of an application framework, neither should authorization.<p>A coherent, formalized, well manageable policy engine can go a great deal for practical organization security