devise-two-factor VS warden

Your authentication mechanism should include multiple factors, something the user knows and something the user has. If you are using Devise, you can use the devise-two-factor gem. If you have custom authentication, you can use the rotp gem to generate OTP codes and verify those during login.

In Ruby-on-Rails it's part of the authentication framework Devise https://github.com/tinfoil/devise-two-factor and related modules including creating QR codes, backup codes etc. PHP Laraval has similar libraries https://jetstream.laravel.com/2.x/features/two-factor-authen...

Auth0 and similar commercial companies might very good at marketing. Try replacing "API" with "library" or a programming language name.

> It's just not valuable enough for anyone to create

For a commercial API you need to charge $10 USD/month, or equivalent in terms of per-API-call, otherwise your service won't be profitable. You call 5 US cent already expensive, so I think you're right, it's not valuable enough.

I've used https://github.com/tinfoil/devise-two-factor before – it's good to know there is a maintained alternative that implements the UI already and is compatible to Rails 7.

Are you referring to the devise two factor authentication gem at https://github.com/tinfoil/devise-two-factor? If so, I have posted a ticket that modifies the gem to use the Rails 7 Active Record encryption capabilities and some folks have been asking if a pull request could be created for it. There is some discussion going on in the issue thread on how to proceed. See https://github.com/tinfoil/devise-two-factor/issues/192 for details.

devise-two-factor: https://github.com/tinfoil/devise-two-factor

Devise is build on top of another library and if you ever had to customize Devise, you probably saw that underlying lib. It is called Warden

Devise is an authentication library built on top of Warden, a Rack-based authentication framework.

In general, even though the Hanami ecosystem lacks any "plug-and-play" solutions such as Devise, you can use many existing libraries not tightly coupled to Ruby on Rails. For authentication, you can use Warden, OmniAuth or Rodauth. For uploads there is Shrine. The pagination is built into ROM. Integration with exception catchers such as Rollbar is easy.

There hasn't been a lot that has changed to how sessions are managed. Warden itself hasn't had much by way of updates in years, but you didn't even mention that.

Do you use system tests in authlogic? Devise (or more precisely, Warden) has has a helper that sets the user on next request.

Devise is probably the most popular option out there. If you're learning to apply your skills in the wild then I'd recommend Devise. In my opinion, there's a learning curve, especially if you want to customize it more. You can also learn the underlying Ruby gem called warden.

Warden perhaps? It's the actual authentication part Devise uses.

Despite this approach works, it's polluting the controller with authentication logic. Given that Devise uses Warden under the hood, the same can be achieved by taking advantage of warden callbacks that will always get executed when a meaningful event is triggered.