The code in OwinExtensions.cs that attempts to retrieve an IDataProtectionProvider from IAppBuilder and then if that's null create an instance of Microsoft.Owin.Security.DataProtection.DpapiDataProtectionProvider using the default ctor needs to be removed. The parameterless ctor has been obsoleted from Microsoft.Owin.Security.
Instead, SignalR should simply call the GetDataProtector() extension method on IAppBuilder and inject that into the dependency resolver.
It's been obsoleted and isn't even released yet. Epic.
Should I use CreateDataProtector(this IAppBuilder app, params string purposes)? It looks to me that CreateDataProtector cannot return null. Is that the case? What about on Mono?
Use CreateDataProtector instead of the deprecated GetDataProtectionPr…
- This unfortunately removes the ability to fall back to DefaultProtectedData
Don't call the deprecated parameterless DpapiDataProtectionProvider ctor