Clearance VS warden

https://github.com/thoughtbot/clearance It is simple and good. You can also customize it easily.

Clearance has been better for most of my projects. Its got a cleaner implementation that Devise, and comes with a generator that will optionally dump all of the basic routes and views into the standard locations which you can then edit at will.

I tend to suggest Clearance for Rails apps that need a more focused toolset. It may not do everything that Devise does, but it definitely works well with Rails 7. https://rubygems.org/gems/clearance/versions/2.5.0

I've found a much simpler/cleaner authentication gem is Clearance. Devise does just about everything, but Clearance is more opinionated so out of the box it does more of what you normally want.

...because some folks prefer clearance to devise! :-D

Clearance is a Rails authentication with email & password. It is intended to be small, simple, and well-tested. It has opinionated defaults but is intended to be easy to override. 3,321 stars by now

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.