Standalone login requires password hash to be stored in the database. However, for OAuth authentication, we do not store user’s password hash. As such if an app that offers standalone login and social login do we need to maintain separate table?
If assuming we maintain separate table, does that mean we need to have 2 user model?
Anyone can share their experience on this?