Peoplefinder Alternatives

Similar projects and alternatives to peoplefinder

spicedb

38 4,543 9.7 Go peoplefinder VS spicedb

Open Source, Google Zanzibar-inspired permissions database to enable fine-grained access control for customer applications
policy-aona

1 2 0.0 Open Policy Agent peoplefinder VS policy-aona
SurveyJS

surveyjs.io featured

Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better peoplefinder alternative or higher similarity.

Suggest an alternative to peoplefinder

peoplefinder reviews and mentions

Posts with mentions or reviews of peoplefinder. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-16.

Aserto, the developer API for permissions and RBAC, is open to all
3 projects | news.ycombinator.com | 16 Feb 2022

That's indeed why authorization is a harder problem than authentication - because much of it is domain-specific.
Still, there are many things an authorization system can help with. For example, the service/organization affiliation of the user is easily expressed as a set of attributes / properties / roles on the user. If that's stored in a central directory, and the authorizer has a cached copy, you can use this context as part of your policy for making authorization decisions.
Lifting the authorization policy into a central repo allows you to consolidate authorization logic, and also enables separation of concerns. SecOps can evolve the authorization policy of the application without having to ask developers to revisit the logic in all the places it exists. In fact, we have customers that have their secops team deploy new versions of the authorization policy without having to redeploy the application.
Another example is having front-end code that can dynamically render component state (visible or enabled) based on the same authorization rules that the back-end / API uses. We have nice examples of this in our "peoplefinder" demo [0], which you can launch as a quickstart [1].
[0] https://github.com/aserto-demo/peoplefinder
[1] https://www.aserto.com/quickstarts