NCache protects distributed caches with layered security (authentication, authorization, encrypted communication, and data encryption) without compromising performance or scalability. It integrates with Microsoft Active Directory and LDAP, so you manage access centrally, and supports password-less gMSA/Kerberos authentication for Windows applications. Security works on Windows Server on-premises and in Azure, AWS, and Google Cloud, as well as on Linux, Docker, and Kubernetes.
NCache authenticates Node Admins and Cache Users against Microsoft Active Directory or other LDAP-compatible directory services, on Windows or Linux cache servers. You grant NCache permissions to existing domain users and groups, so there is no separate NCache user directory to maintain, and your existing password policies and account restrictions still apply.
Connect using Active Directory/LDAP credentials:
using Alachisoft.NCache.Client;
var options = new CacheConnectionOptions();
options.Security = SecurityOptions.CreateWithCredentials("your-username", "your-password");
ICache cache = CacheManager.GetCache("demoCache", options);
In production, obtain credentials from a secure source rather than hardcoding passwords.
Client applications can authenticate with a Windows Group Managed Service Account (gMSA) instead of storing usernames and passwords in configuration files. Active Directory generates and rotates the gMSA password automatically, and Windows-native Kerberos handles authentication. One managed identity can be shared across authorized application servers and administered with existing Active Directory tools.
gMSA suits Windows applications such as ASP.NET and ASP.NET Core apps, IIS application pools, Windows Services and background processes, and legacy .NET Framework or modern .NET applications across Windows Server farms.
Connect using Windows gMSA for password-less authentication:
using Alachisoft.NCache.Client;
var options = new CacheConnectionOptions();
options.Security = SecurityOptions.CreateWithGMSA();
ICache cache = CacheManager.GetCache("demoCache", options);
The application must run under an authorized gMSA identity.
Note: gMSA is supported for Cache Users (meaning NCache client applications). Node Admins authenticate with their Active Directory/LDAP user credentials.
NCache client applications on Windows Server VMs in Azure, AWS, and Google Cloud can authenticate through a managed Microsoft Active Directory service, self-managed domain controllers, or your existing on-premises Active Directory. Each managed service provides LDAP, Kerberos, and Windows domain capabilities, so your current Windows security model carries over to the cloud without a new NCache authentication model.
| Authentication Option | Azure | AWS | Google Cloud |
|---|---|---|---|
| Managed Microsoft AD | Entra Domain Services | AWS Managed Microsoft AD | Managed Microsoft AD |
| Self-Managed Active Directory | Azure VMs | EC2 | Compute Engine |
| On-Premises Active Directory | VPN / ExpressRoute | VPN / Direct Connect | Cloud VPN / Interconnect |
| LDAP Authentication | Supported | Supported | Supported |
| Kerberos / Windows gMSA | Available* | Available* | Available* |
| Windows Server VMs | Supported | Supported | Supported |
*Windows gMSA requires compatible domain services, domain configuration, and supported application/NCache integration. Validate specific managed-directory combinations before production deployment.
NCache separates administrative access from application cache access. NCache servers enforce permissions, so each authenticated identity can perform only the operations its access level allows.
Permissions are assigned to Active Directory/LDAP users and groups at three boundaries: machine level (operating system administrators control local privileges), node level (who can manage NCache servers), and cache level (which applications and users can access each cache). This supports least privilege by keeping cache management separate from data access.
Add an Active Directory account as a Node Admin:
$nodeAdmin = Get-Credential
Add-NCacheUserOrGroup -Server 20.200.20.11 `
-AccessLevel Admin `
-NodeAdminCredentials $nodeAdmin `
-UserOrGroupName david_watson `
-UserOrGroupDN "CN=David Watson,OU=engineers,DC=example,DC=com" `
-DomainController domain_controller
Grant that account Cache User access to a specific cache:
Add-NCacheUserOrGroup -Server 20.200.20.11 `
-AccessLevel Cache `
-CacheName defaultCache `
-NodeAdminCredentials $nodeAdmin `
-UserOrGroupName david_watson `
-UserOrGroupDN "CN=David Watson,OU=engineers,DC=example,DC=com" `
-DomainController domain_controller
These examples assume NCache security is enabled and the directory user exists. Replace the sample server, cache, account, distinguished name, and domain controller with your own values.
NCache encrypts network communication with TLS 1.2 and TLS 1.3 on Windows and Linux, protecting data in transit from interception. You can secure whichever paths your architecture requires: client-to-server, server-to-server within a cluster, Bridge traffic between geographically separated clusters, and supported management channels.
NCache can generate, sign, and provision server certificates and renew them before they expire, with no manual replacement of certificate files. Each server keeps its own certificate and private key, and private keys never leave their machines. You can use certificates from your own Certificate Authority instead, and TLS/mTLS is configured the same way on Windows and Linux, which simplifies certificate management across many servers.
TLS protects data on the network; Data Encryption protects the cached data itself. When enabled, the NCache client SDK encrypts application data inside the client process before sending it to the cache servers, which keep it encrypted in memory and during replication. Authorized clients decrypt it transparently on retrieval, with no application coding involved. This protects confidential information even if cached data is accessed at the memory or storage level.
Administrative access is authenticated and authorized separately from application cache access, so application users cannot perform management operations.
TLS/mTLS and data encryption are available in all of these environments. Authentication and authorization depend on the deployment method.
Whether you run legacy .NET Framework applications, modern .NET applications, or containerized workloads, NCache protects application access, network communication, and cached data using your existing Windows and Active Directory infrastructure, on-premises, in the cloud, or on Linux.
© Copyright Alachisoft 2002 - . All rights reserved. NCache is a registered trademark of Diyatech Corp.