AspNetCore.DataProtection.NCache
5.3.7
dotnet add package AspNetCore.DataProtection.NCache --version 5.3.7
NuGet\Install-Package AspNetCore.DataProtection.NCache -Version 5.3.7
<PackageReference Include="AspNetCore.DataProtection.NCache" Version="5.3.7" />
<PackageVersion Include="AspNetCore.DataProtection.NCache" Version="5.3.7" />
<PackageReference Include="AspNetCore.DataProtection.NCache" />
paket add AspNetCore.DataProtection.NCache --version 5.3.7
#r "nuget: AspNetCore.DataProtection.NCache, 5.3.7"
#:package AspNetCore.DataProtection.NCache@5.3.7
#addin nuget:?package=AspNetCore.DataProtection.NCache&version=5.3.7
#tool nuget:?package=AspNetCore.DataProtection.NCache&version=5.3.7
AspNetCore.DataProtection.NCache
NCache Key Storage Provider for the ASP.NET Core Data Protection system. This package lets you persist Data Protection keys in NCache instead of the local file system, enabling key sharing across multiple server instances in a web farm — so cookies, tokens, and other protected payloads remain valid regardless of which server handles the request.
Installation
Install-Package AspNetCore.DataProtection.NCache
or, using the .NET CLI:
dotnet add package AspNetCore.DataProtection.NCache
What is Installed
Installing this package adds the following NCache configuration files to your project:
- client.ncconf — Defines the cache client settings, including the cache name and the list of server nodes the client connects to.
- config.ncconf — Contains the cache configuration (cache topology, partitions, eviction policy, etc.) used when the cache is created/registered.
- tls.ncconf — Contains TLS/SSL settings used to secure communication between the client and the NCache cluster, if enabled.
Prerequisites
- .NET 6.0+ Application.
- NCache SDK 5.3.7.1 or later.
- An NCache 5.3.7 (or later) server should be up and running, with the target cache already created/registered on it.
Getting Started
Setting up NCache
Before running your application (if NCache is not installed on the current machine), you need to update client.ncconf so the client knows which cache to connect to and where to find it:
- Open
client.ncconf. - Locate the cache entry named
myCacheand rename it to the name of your actual cache (the cache you created/registered on the NCache server). - Under the
serversettings, update the server address to point to one of the nodes in the cluster where that cache is running.
Example:
<cache id="myCache" ... >
<server name="10.0.0.1" ... />
</cache>
Change myCache → YourCacheName, and 10.0.0.1 → the IP/hostname of a node hosting YourCacheName.
Setting up Package
Register NCache as the Data Protection key storage provider in Program.cs:
var builder = WebApplication.CreateBuilder(args);
// Read NCache settings from appsettings.json
var cacheName = builder.Configuration["NCacheSettings:CacheName"] ?? "demoCache";
var appId = builder.Configuration["NCacheSettings:ApplicationId"] ?? "NCacheDataProtectionSample";
var keyName = builder.Configuration["NCacheSettings:KeyName"] ?? "DataProtection-Keys";
builder.Services.AddDataProtection()
.SetApplicationName(appId)
.PersistKeysToNCache(cacheName, keyName);
var app = builder.Build();
app.Run();
Configuration
ASP.NET Core (appsettings.json):
{
"NCacheSettings": {
"CacheName": "YourCacheName",
"ApplicationId": "NCacheDataProtectionSample",
"KeyName": "DataProtection-Keys"
}
}
Adjust cache name and other settings as needed for your environment.
Resources
Technical Support
Alachisoft provides various technical support resources.
Visit the Alachisoft Support Center to select a support resource appropriate for your issue. To request additional features or report a documentation discrepancy, contact support@alachisoft.com.
License
Copyright © 2026 Alachisoft. All rights reserved.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
| .NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
| .NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
| .NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
| MonoAndroid | monoandroid was computed. |
| MonoMac | monomac was computed. |
| MonoTouch | monotouch was computed. |
| Tizen | tizen40 was computed. tizen60 was computed. |
| Xamarin.iOS | xamarinios was computed. |
| Xamarin.Mac | xamarinmac was computed. |
| Xamarin.TVOS | xamarintvos was computed. |
| Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Alachisoft.NCache.SDK (>= 5.3.7.2)
- Microsoft.AspNetCore.DataProtection (>= 7.0.2)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.