Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more

ASP NET Identity migration not working if previously used with Commerce DB

Vote:
 

I'm upgrading from Commerce 13.32.5 to 14.5.0, and one step is to upgrade ASP NET Identity. There's a built in migration for this, located in EPiServer.Cms.UI.AspNetIdentity.Schema.AspNetIdentitySchemaUpdater<TUser>. However, this script does not work if you're targeting the Commerce DB, due to it also including transactions to tblBigTable, amongst others.

I don't have to store users in the Commerce DB, but now that it is the current case - I want to continue doing so. Also, if this is not supported - you should update Foundation to account for this, as that project also uses the Commerce DB for ASP NET Identity users.

#288765
Oct 06, 2022 14:55
Vote:
 

I believe we are looking into this, bug CMS-24819

#288993
Oct 11, 2022 7:49
Andreas J - Oct 11, 2022 12:21
Thanks!
Vote:
 

This was fixed in EPiServer.CMS.UI 12.13.2

#295360
Jan 26, 2023 0:18
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.