Password (hash) doesn't match when re-using existing Microsoft Identity user tables
<p>We have an existing SQL database with <strong>Microsoft Identity</strong> tables, originally generated by a ASP.NET Core app.</p>

<p>We also have an ASP.NET 4 app, which also uses Microsoft Identity.</p>

<p>We'd like the ASP.NET 4 app to be able to <strong>validate logins using the same database</strong> as the original .NET Core app.</p>

<p>However, when we try to validate passwords, they don't match.</p>

<p>I'm just guessing that the password hashes generated by the .NET Core app cannot be validated by the ASP.NET 4 app, but I'm not sure where to go from here. :)</p>

<p>There's no custom password hashing in the .NET Core app, and I'm struggling to find any config that might affect hashing?</p>

<p>Any help or pointer is greatly appreciated!</p>

<p><strong>Edit:</strong> It seems this may be caused by different hashing algorithms in Identity V2/V3. Not sure how to mimic the V3 hashing algorithm in the ASP.NET 4 app, though.</p>