"Email [email protected] has already been taken." handling

[briskt]

When a user cannot be created due to a conflicting email (or other field) an attempt should be made to override with new data from the id-broker. Often this error occurs when a change has been made in the id-broker database, but the equivalent change was not made in the pw-api database. Since the pw-api user table is effectively a cache of the idp-broker user table, changes should seamlessly propagate to the "cache".

It should also be considered whether it is worth keeping this local copy of the user table. It could be that pw-api data (e.g. password resets, event log) should be the only thing stored locally.