rodauth-oauth VS rodauth-model

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.

Finally, let's also modify the remove form to display nicknames instead of last used timestamps (we're using the Account#webauthn_keys association defined by rodauth-model):

While I love this decoupling, it would still be nice to be able to at least create accounts and retrieve associations directly through the model. So, I created the rodauth-model gem, which provides an interface similar to Active Record's has_secure_password, and defines associations based on your Rodauth configuration (together with associated models).