Action Policy VS keygen-api

Action Policy is a flexible, extensible, and performant authorization framework for Ruby and Rails apps. It uses multiple caching strategies out of the box, making it very fast, especially if your authorization rules require database queries.

Action Policy is the latest Authorization framework I've seen recommended. What is more, it is maintained by the nice and experienced team from Evil Martians.

Lots of goodies here, such as token authentication, role- and permission-based authorization (including a move from Pundit to ActionPolicy), and how I test the API end-to-end using *raises flame shield* Cucumber.

Also, ActionPolicy is better than Pundit for most applications. Give it a try.

Use Action Policy or Pundit, and write tests for your policies. Authz is worth testing with near complete coverage.

You may ask what's makes Active Entry better or different from other gems like Pundit, Action Policy (especially), or CanCanCan.

At work, we've recently faced similar issues and moved to ActionPolicy as a result. It's designed slightly differently, but there is a lot of overlap with what John came up with.

I don't have an Elixir background, but I absolutely utilize pattern matching in my Ruby code bases:

- https://github.com/keygen-sh/typed_params/blob/4e4982b7d2b26...

- https://github.com/keygen-sh/typed_params/blob/4e4982b7d2b26...

- https://github.com/keygen-sh/keygen-api/blob/master/app/migr...

- https://github.com/keygen-sh/keygen-api/blob/36cd61db143cc1c...

- https://github.com/keygen-sh/typed_params/blob/4e4982b7d2b26...

I love it. I want even more pattern matching too, like with defp: https://bugs.ruby-lang.org/issues/19764.

Honestly, I don't have many resources to provide. I read a lot of policy tests via GitHub search (e.g. path:spec/policies/*/*.rb), but couldn't find anything that looked like what I wanted. I wrote the DSL as-needed in order to fully test my app's authz while migrating from Pundit to ActionPolicy.

It's not the prettiest when you actually look beneath the covers [0], but it does what I wanted -- provides a way to write exhaustive authz tests. Without the DSL, I probably wouldn't have written. The PR for said migration was massive [1], and was a precursor to going open source [2].

[0]: https://github.com/keygen-sh/keygen-api/blob/master/spec/sup...

[1]: https://github.com/keygen-sh/keygen-api/pull/647

[2]: https://github.com/keygen-sh/keygen-api/issues/644

Yes, I can see why you might make this argument. [1]

[1] https://github.com/keygen-sh/keygen-api/blob/master/LICENSE....

And not at all set on WorkOS. It just looked like the easiest way to set up SSO last time I researched the topic. Feel free to comment on the issue with any recommendations.

Since when can you run heroku pg:upgrade to switch database tiers? I was following an upgrade sequence I put together over the years [^0], but I guess Heroku automated this at some point? What would be really funny is if this had been possible all long...

[^0]: https://github.com/keygen-sh/keygen-api/blob/master/.notes/d...

Maybe use keygen-sh?

I run a business called Keygen [^0], and own the @keygen namespace on npm. We’re working on a Node SDK, so this isn’t good to hear. I’ll open up a discussion with them and see what we can do.

[^0]: https://keygen.sh

- org-2.php.pkg.github.com/package

I wonder if that had any impact on their decision.

[0]: https://github.com/keygen-sh/keygen-api/issues/490