-
Notifications
You must be signed in to change notification settings - Fork 87
Cannot unprotect data after upgrading .NET Framework app to new DataProtection version #187
Comments
I have exactly the same issue, but since i have a custom dataprotectionrepository i just do this before loading the xml rawxmlstring = rawxmlstring.Replace(
"Microsoft.AspNetCore.DataProtection, Version=1.0.0.0,",
"Microsoft.AspNetCore.DataProtection, Version=1.1.0.0,"); it would be nice if i didn't have todo this tough, since this also won't create a new key that uses the new assembly version |
@pakrym thoughts? |
Any updates on this issue? Would hate to run into this problem again when the next version is released. |
@nphmuller , have you tried downgrading Kestrel to 1.0.2? I've had some similar weird issues in regards to using OpenId while having everything on 1.1. |
@muratg could that be fixed in the next milestone to make sure the same issue doesn't reproduce when moving from 1.x to 2.0? |
@natemcmaster I just hit this error again when migrating DataProtection from 1.1.1 to 1.1.2. Is this expected until this fix goes live? |
Try updating/ adding System.Web.Http and see if that fixes?
…Sent from my Windows 10 phone
From: Kyle Spearrin<mailto:notifications@github.com>
Sent: Saturday, May 20, 2017 10:54 AM
To: aspnet/DataProtection<mailto:DataProtection@noreply.github.com>
Cc: Jeremy Sinclair<mailto:jeremy.sinclair@live.com>; Comment<mailto:comment@noreply.github.com>
Subject: Re: [aspnet/DataProtection] Cannot unprotect data after upgrading .NET Framework app to new DataProtection version (#187)
@natemcmaster<https://github.com/natemcmaster> I just hit this error again when migrating DataProtection from 1.1.1 to 1.1.2. Is this expected until this fix goes live?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#187 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AD1Ipd3BJL-sGSk5Rm1AwdL4BLZjlUafks5r7v6ygaJpZM4K7FYo>.
|
The fix is in 2.0.0-preview1. It wasn't included it in 1.1.2. I've opened #235 as a separate issue to consider/discuss backporting this fix to 1.x. |
An exception is thrown when I try to unprotect data in release 1.1.0 which was protected with release 1.0.0. This only happens when I target the full .Net Framework stack (only tested net462). When I target netcoreapp everything runs smoothly.
Seems like there are some differences between .Net Full and .Net Core in the way library versions are bound. In issue #153 almost the same problem happens.
These are the exception details:
I wrote a small app that demonstrates my problem:
project.json:
Program.cs:
And the key file (key-68f4e377-536d-4384-a6e1-a4309d2a1282.xml).
Place it in '%LocalAppData%\ASP.NET\DataProtection-Keys' (or change the line of code).
Don't worry, the key was created only for this issue ;)
The text was updated successfully, but these errors were encountered: