So in my mind, the usual users table that we are used to having, is going to split in two:
- whatever data is within the Identity Provider
- the domain specific data (user.facialHairStyle) is going to still stay in the user table. One difference is that it will be missing the regular properties covered by the Identity Provider: name, sex, mail...
Gotta be honest. I far from like this. First dumb example that comes to mind: User registers, the app handles that by creating a user entry with domain-specific data with id of the identity pool entry. What if the user entry creation fails? Do I need to invent rollback procedures? Do I unregister the user?