The implementation of the
<machineKey> element in ASP.NET is replaceable. This allows most calls to ASP.NET cryptographic routines to be routed through a replacement data protection mechanism, including the new data protection system.
The new data protection system can only be installed into an existing ASP.NET application targeting .NET 4.5.1 or higher. Installation will fail if the application targets .NET 4.5 or lower.
To install the new data protection system into an existing ASP.NET 4.5.1+ project, install the package Microsoft.AspNetCore.DataProtection.SystemWeb. This will instantiate the data protection system using the default configuration settings.
When you install the package, it inserts a line into Web.config that tells ASP.NET to use it for most cryptographic operations, including forms authentication, view state, and calls to MachineKey.Protect. The line that’s inserted reads as follows.
<machineKey compatibilityMode="Framework45" dataProtectorType="..." />
You can tell if the new data protection system is active by inspecting fields like
__VIEWSTATE, which should begin with “CfDJ8” as in the example below. “CfDJ8” is the base64 representation of the magic “09 F0 C9 F0” header that identifies a payload protected by the data protection system.
<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="CfDJ8AWPr2EQPTBGs3L2GCZOpk..." />
The data protection system is instantiated with a default zero-setup configuration. However, since by default keys are persisted to the local file system, this won’t work for applications which are deployed in a farm. To resolve this, you can provide configuration by creating a type which subclasses DataProtectionStartup and overrides its ConfigureServices method.
Below is an example of a custom data protection startup type which configured both where keys are persisted and how they’re encrypted at rest. It also overrides the default app isolation policy by providing its own application name.
using System; using System.IO; using Microsoft.AspNetCore.DataProtection; using Microsoft.AspNetCore.DataProtection.SystemWeb; using Microsoft.Extensions.DependencyInjection; namespace DataProtectionDemo public class MyDataProtectionStartup : DataProtectionStartup public override void ConfigureServices(IServiceCollection services) services.AddDataProtection() .SetApplicationName("my-app") .PersistKeysToFileSystem(new DirectoryInfo(@"\serversharemyapp-keys")) .ProtectKeysWithCertificate("thumbprint");
You can also use
<machineKey applicationName="my-app" ... /> in place of an explicit call to SetApplicationName. This is a convenience mechanism to avoid forcing the developer to create a DataProtectionStartup-derived type if all they wanted to configure was setting the application name.
To enable this custom configuration, go back to Web.config and look for the
<appSettings> element that the package install added to the config file. It will look like the following markup:
<appSettings> <!-- If you want to customize the behavior of the ASP.NET Core Data Protection stack, set the "aspnet:dataProtectionStartupType" switch below to be the fully-qualified name of a type which subclasses Microsoft.AspNetCore.DataProtection.SystemWeb.DataProtectionStartup. --> <add key="aspnet:dataProtectionStartupType" value="" /> </appSettings>
Fill in the blank value with the assembly-qualified name of the DataProtectionStartup-derived type you just created. If the name of the application is DataProtectionDemo, this would look like the below.
<add key="aspnet:dataProtectionStartupType" value="DataProtectionDemo.MyDataProtectionStartup, DataProtectionDemo" />
The newly-configured data protection system is now ready for use inside the application.