rodauth-rails VS rails-authentication-from-scratch

In this article, I would like to show how to set each of these up in a Rails app that uses rodauth-rails. I'll be using Safari on macOS Ventura, and have iCloud Keychain sync enabled, which is a requirement for Apple passkeys.

Once I felt things were functioning well enough, I extracted the glue code into the rodauth-rails gem and added tests. I also included an install generator, which created the initial skeleton with sensible default configuration. A new Roda superclass provided a convenience configure method for loading the Rodauth plugin together with the rails feature.

FWIW I'm using rodauth and I like it: https://github.com/janko/rodauth-rails

My question is pretty much in the title. Is it possible to do Omniauth in a Rails API Only app? I've been looking into devise-token-auth and rodauth-rails. rodauth-rails has a tutorial for Omniauth (https://github.com/janko/rodauth-rails/wiki/OmniAuth), but it is using a Rails monolith.

I didn't create it, it was created by Jeremy Evans, I just contribute to it occasionally ;). I created the Rails integration, because I wanted to bring it into the Rails ecosystem, and I recently started recording screencasts. So I'm biased in that sense :)

maybe https://github.com/janko/rodauth-rails

$/myapp> bundle info rodauth-rails * rodauth-rails (0.18.1) Summary: Provides Rails integration for Rodauth. Homepage: https://github.com/janko/rodauth-rails Path: /Users/shino/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rodauth-rails-0.18.1

I don't know if you've seen, but I wrote a guide that shows an integration, which you can use for now. This is also what the official demo Rails app uses.

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.