Consider adding AspNetCore.DataProtection.ServiceFabric to the documented options
MedAnd opened this issue · 7 comments
Consider adding AspNetCore.DataProtection.ServiceFabric as an option?
We don't appear to have a page for 3rd party providers that I can see on the docs site. Am I missing something?
Hi @blowdart,
On the Key storage providers page there is a references to another 3rd party library, StackExchange.Redis ConnectionMultiplexer... not the same I know but wondering if you would consider links to 3rd party key providers?
That's slightly different, as we wrote the providers here, just not the backing store. Given the sensitivity of the library I'm not sure I'd be comfortable seeing something in official docs pointing to a 3rd party. However if you look at identity, https://github.com/aspnet/identity you can see we have 3rd party options in the repo home page. Would that work for you?
Understand re: sensitivity in official docs, especially around security related components. Worth asking though as I noticed other teams such as EF Core team have 3rd party providers listed on the Database Providers page. They used a warning such as:
I think it would help the .Net Core community to at least have a new section, maybe "Community Maintained Key Providers" in aspnet/DataProtection if that is acceptable?
I'd rather do the same as identity and keep it in the source repo rather than docs,
Did you want a pull request to update the repo landing page or you guys will?
Done.