We should consider backing out be8232d since identity service didn't make it into 2.0, this would give us more time to react/update things without having backcompat issues.

The main motivation from my perspective is not introducing a 2.0 schema change that only adds 2 properties, that seems like a waste.

There doesn't appear to be anything preventing us from bringing all of this back as a new feature in 2.1 as it doesn't affect anything outside of the EntityFrameworkCore.

We'd also back out the new activity/sign in/ password feature as well since that's what drove the schema changes.

cc @ajcvickers @divega @blowdart