rails-authentication-from-scratch VS warden

You can certainly roll your own authentication with Rails and feel very confident about it. One such example: https://stevepolito.design/blog/rails-authentication-from-scratch

The owasp cheatsheet is probably the best resource https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html, there's also this rails tutorial https://stevepolito.design/blog/rails-authentication-from-scratch that incorporates some (but not all) good practices that covers implementation details, but are broadly applicable to any language and framework

Devise not being Hotwire compatible is a huge turnoff for me. Honestly if I were staring a new project today I’d probably go with a “hand rolled” authentication. I haven’t done it myself but I know a lot of thought was put into this guide if you were interested in that route: https://stevepolito.design/blog/rails-authentication-from-scratch/

For those who are interested in building their own authentication, I would also recommend reading https://stevepolito.design/blog/rails-authentication-from-scratch/

I will not go fully in detail about how to make your own Authentication from scrap, although a really useful blog that does do that can be found here. I will be going over the logic behind it.

This looks promising and I'd love to have the full control on my application. And recently I went through this repo https://github.com/stevepolitodesign/rails-authentication-from-scratch with a lot of details on how Devise works under the hood. It makes it really easy to understando all the different chunks of code and how the work all together.

Thank you for the feedback! I went ahead and opened some issues around these points. One of the advantages to creating and promoting this guide is that lots of folks can review my work and make improvements.

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.