Aspnetcore.docs: Custom Storage Providers for ASP.NET Core Identity

[danroth27]

Port http://www.asp.net/identity/overview/extensibility/overview-of-custom-storage-providers-for-aspnet-identity to ASP.NET Core Identity

See https://github.com/aspnet/Identity/issues/1113

Yeah we shouldn't call it the UOW pattern since its not exactly that, best to just be explicit and say something to the effect of: "Stores should only persist changes in the CreateAsync/UpdateAsync/DeleteAsync methods of base Store interface, any other store method should only manipulate the entity without persisting the changes."

Overall structure same as previous article; Hao and Steve will work together to update it.

Main changes: removed TKey from all interfaces. The key is now always a string to identity - it's up to the provider to convert that string into its type.

[DeluxZ]

Any update on this?

[danroth27]

@blowdart Not yet - it's still on our backlog

[jorgeyanesdiez]

+1 for this, I'm trying to get rid of the EF dependency and this would come handy.

[CodingSamurai]

+1 This is essential functionality if people are going to be moving to .NET Core for production apps.

[StephanZahariev]

+1, I'm also trying to get rid of the EF dependency

[AbdoDabbas]

+1, when do you expect to get it done ?

[alex521]

+1

[danroth27]

@HaoK @blowdart There's quite a bit of customer interest in getting this content out sooner. Is this something you guys could help out with?

[HaoK]

I can take a pass over the old article and see what needs updating

[jrgunawan]

+1

[dntim]

Folks, any news?

[danroth27]

This is actively being worked on and should be published in the next few weeks.

[Greatsamps]

are we getting close yet?

[rushfive]

+1 any updates on the progress?

[krunalrspl]

Any update on this?

[RobVargaCH]

Still no update guys? Very keen to remove this EF dependency...

[danroth27]

I believe @ardalis will have a PR out for this shortly

[ardalis]

This week!

[RobVargaCH]

Hi Guys, thanks very much for getting this out; all looks good and clear. One small recommendation I have is that in Steve's code the ApplicationUser inherits from ClaimsIdentity: this may confuse some users and maybe a quick one-liner about implementing IIdentity as an alternative may be helpful.

Thanks again.

Cheers,
Rob

[ardalis]

@RobVargaCH Thanks, I updated the sample in the PR to use IIdentity instead of ClaimsIdentity, along with a couple of other minor tweaks.