bouncer VS CASL

Bouncer on the other hand supports scoped permission assignments where the assigned permission applies to a specific model only.

That'd be great honestly, but I haven't found anything similar yet. I took a look at Bouncer but it doesn't seem to solve the problem either, just resource-based authorization too.

As well as using Spatie's Laravel Permission package, there are other packages that can be used to add roles and permissions to your application. For example, you could use Bouncer or Laratrust.

There are a few open source Laravel packages for managing roles and permissions. See https://github.com/spatie/laravel-permission or https://github.com/JosephSilber/bouncer.

In this tutorial, you'll learn how to implement RBAC in Laravel using Bouncer. Bouncer is a PHP package that lets you add roles and abilities to your Eloquent models.

I only have experience with Bouncer but it has worked well for me. As a basic hypothetical scenario, you can create different roles and abilities such as:

Another option is bouncer https://github.com/JosephSilber/bouncer

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