CASL VS accesscontrol

You can find numerous libraries dedicated to authorization, depending on the language you use. For example, CASL is a Javascript library that helps you model flexible authorization schemes utilizing a set of declarative APIs. The “give me the list of Article readable to the current user” problem can be modeled and queried like the following:

You must do something like ACL, Cognito layer isn't the way to achive what do you want to do. Remember, Cognito isn't nothing more than an 3rd party authorization provider with user pools, restricted access to your own resources must be handled in your logic app layer instead Cognito. However I suggest you to read about ACLs (can you check out this ie https://github.com/stalniy/casl) and differences between ACLs and authentication providers.

PS If you do mobile / web work (or something else with "detached" UI), I find that declarative access control rules are far superior to imperative ones, because they can be serialized and shipped over the wire. For example, backend running cancancan can be easily send the same rules to casl on the frontend, while if you used something like pundit to secure your backend, you either end up re-implementing it in the frontend, or sending ton of "canEdit" flags with every record.

I'm trying to integrate @casl/vue with Vue 3, and I'm afraid I'm having problems.

Do you have any experience? How does it compare to other alternative like https://casbin.org, https://casl.js.org? There are tons of libraries, actually I'm little bit lost.

CASL

You can mitigate the pain by using libraries like accesscontrol, express-rbac, django-guardian, etc., to manage authorization more declaratively. But making sure nothing leaks is still a significant challenge.

2- https://www.npmjs.com/package/accesscontrol https://github.com/onury/accesscontrol

I used nestjsx-crud in the api we prepared. This library makes CRUD operations very easy. However, there is no support on the authorization side. That's why I made use of the accesscontrol library, which can be easily integrated with both nestjs and refine.

Access-Control

not a big fan of DSL(s), I think it adds complexity to the code, checkout this library accesscontrol all the configuration is javascript objects and more maintainable I think.

I am going through the docs accesscontrol npm library and came across code to limit the user to only readOwn resources.

what do you think about this library accesscontrol. It seems easier to grasp with its fluent syntax and no custom DSL