rodauth-omniauth VS rodauth-oauth

In this article, I show how to set up the rodauth-omniauth gem I had created in a Rails app, and customize the flow. This gem provides a much more integrated solution compared to Devise, in the sense that it implements the OmniAuth callback phase, automatically registering the user and/or logging them in, and persisting their external identities. It supports multiple providers, and essentially codifies this OmniAuth guide.

While Devise provides a convenience layer around OmniAuth, it does nothing to actually sign the user into your app. When I started writing the OmniAuth integration for Rodauth, I wanted to go one step further and actually handle things like persistence of external identities, account creation and login, while still allowing the developer to customize the behaviour. That's how rodauth-omniauth was created. ✨

It depends on what you mean by OAuth 2.0. If you want your app to be an OAuth 2.0 provider, then you'd use rodauth-oauth. If you want to enable your users to login through external apps that implement the OAuth 2.0 protocol, then OmniAuth is what you'd use. Not all external apps implement login via the OAuth 2.0 protocol, those that do will have their OmniAuth strategies inherit from omniauth-oauth2.

I want to make it easier for 3rd-party Rodauth extensions to provide migrations/views for Rails generators. The rodauth-oauth gem currently provides its own generators (rodauth:oauth:install and rodauth:oauth:views), but it would be nice if they didn't have to be duplicated.