warden VS Sorcery

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.

I have been using devise for a while and it has consistently given me issues. I have wistfully been staring at sorcery for a while now but cant justify the switch since devise is already in the project.

I made a 8 minutes video tutorial (following the wiki: https://github.com/Sorcery/sorcery/wiki/Simple-Password-Authentication) to introduce how to build a simple password authentication feature with Sorcery. With some minor modification to please Turbo.

We'll be installing Sorcery based off this tutorial in their wiki. I'm modifying a little bit since we are creating something different, but also because their tutorial is a bit outdated since it is based off an older version of Rails.

But does it have to be so soon? There are other areas where I'm just as ignorant as I was about the inner workings of authentication (see "the database" below), and in these areas there's not a gem that can automatically solve the problem for me—which is what I've ended up doing for authentication in my own project: even though I could build authentication from scratch, instead I'm using an authentication gem because the effect is exactly the same, but with less code in my app for me to maintain. (Rather than Devise, I've chosen the more lightweight alternative Sorcery. It's simple enough that I can still understand and control the authentication flow, while also providing enough conveniences that I don't have to write out implementation details from scratch.)

Also Sorcery is, despite its name, a little less magic than Devise.

sorcery