• Facebook
  • Twitter
  • Youtube
  • LinkedIn
  • RSS
  • Docs
  • Comparisons
  • Blogs
  • Try NCache
  • Contact Us
Try NCache
Show / Hide Table of Contents

Enable-NCEncryption

This PowerShell cmdlet enables client-side encryption on a specified cache. When encryption is enabled, all data is encrypted at the client before being transmitted to the cache server and is stored in encrypted form at rest. Encrypted data is decrypted when accessed by authorized clients, ensuring protection during both data-in-transit and data-at-rest. This cmdlet is used to secure sensitive cache data by enforcing client-side data protection.

Enable-NCEncryption -Key -Provider `
                    [-Server] [-Port] `
                    [-TlsCertPath] [-TlsCertPassword] `
                    -CacheName [-Credentials]

Examples

  • This command enables the encryption on the cache server 20.200.20.11 for the defaultCache.
Enable-NCEncryption -CacheName defaultCache -Server 20.200.20.11 `
                    -Key txujoegdxzwiophd -Provider TripleDES128
  • This command enables the encryption on the cache servers 20.200.20.11 and 20.200.20.12 for the defaultCache.
Enable-NCEncryption -CacheName defaultCache -Server "20.200.20.11,20.200.20.12" `
                    -Key txujoegdxzwiophd -Provider TripleDES128
  • This command enables encryption for defaultCache on the specified server using the TripleDES128 provider and the supplied encryption key. It runs from a machine where NCache is not installed and connects to the server using mutual TLS (mTLS). The client certificate C:\certs\client.pem authenticates the machine running the cmdlet, and -TlsCertPassword decrypts the certificate’s password-protected private key. Omit this parameter if the private key is not encrypted.
Enable-NCEncryption -CachName defaultCache -Server 20.200.20.11 `
                    -Key txujoegdxzwiophd -Provider TripleDES128 `
                    -TlsCertPath "C:\certs\client.pem" -TlsCertPassword "clientKeyPassword"
  • This command enables the encryption on the cache servers 20.200.20.11 and 20.200.20.12 for the defaultCache, using credentials for authentication.
Enable-NCEncryption -CacheName defaultCache -Server "20.200.20.11,20.200.20.12" `
                    -Key txujoegdxzwiophd -Provider TripleDES128 `
                    -Credentials(Get-Credential john_smith)

Properties

Note

The parameters with asterisk (*) on their names are the required parameters and the rest are optional.

Parameters Data Types Description Default Value
-Key* <String> Specifies the encryption key that will be used to encrypt and decrypt the cache data. This key must be securely generated and managed to maintain the integrity of the encryption process. -
-Provider* <String> Specifies the encryption algorithm or provider to be used for encrypting the data. -
-Server <String> Specifies the IP address of the server where the target cache is hosted. Multiple server IPs can be provided as a comma-separated list. -
-Credentials <pscredential> Specifies the user credentials required to authenticate and authorize access when setting encryption on a remote cache server. -
-Port <Long> Specifies the port on which the NCache Service is listening. 9803
-CacheName* <String> Specifies the name of the cache where encryption should be configured. -
-TlsCertPath <string> Specifies the path to the client PEM certificate used to authenticate this cmdlet when the target NCache server requires Mutual TLS. This parameter is required for Mutual TLS connections even when the cmdlet runs on an NCache server. The PEM file must contain the private key, leaf certificate, and any intermediate certificates. Relative paths are resolved against the current PowerShell location, and the file must exist. You can generate a client certificate using New-NCacheTlsCertificate. -
-TlsCertPassword <string> Password used to load the encrypted private key in the PEM file specified by -TlsCertPath. Required only when the private key is password-protected. Not needed for an unencrypted private key. The password is used only to load the client certificate for the current command's connections. It is not saved in the NCache server configuration. -

Contact Us

PHONE

+1 214-619-2601   (US)

+44 20 7993 8327   (UK)

 
EMAIL

sales@alachisoft.com

support@alachisoft.com

NCache
  • Edition Comparison
  • NCache Architecture
  • Benchmarks
Try NCache
Pricing
NCache Playground

Deployments
  • Cloud
  • Docker
  • Kubernetes
  • On-Premises
Technical Use Cases
  • ASP.NET Sessions
  • ASP.NET Core Sessions
  • Pub/Sub Messaging
  • SignalR Backplane
  • Internet of Things (IoT)
  • NoSQL Database
  • Stream Processing
  • Microservices
Resources
  • Blogs
  • Foundations
  • Videos
  • Comparisons
  • Shows
  • Whitepapers
  • Articles
  • Tech Talks
  • Magazine Articles
  • Third-Party Articles
Customer Case Studies
  • Testimonials
  • Customers
Support
  • Docs
  • Schedule a Demo
  • Tips
Company
  • Leadership
  • Partners
  • News
  • Events
  • Careers
Contact Us

  • EnglishChinese (Simplified)FrenchGermanItalianJapaneseKoreanPortugueseSpanish

  • Terms of Use
  •  
  • Privacy Policy
  •  
  • Cookie Policy
© Copyright Alachisoft 2002 - . All rights reserved. NCache is a registered trademark of Diyatech Corp.
  • Facebook
  • Twitter
  • Youtube
  • LinkedIn
  • RSS