- Solutions
-
- File Server: Ransomware Protection
- File Server: File Copy
- File Server: Audit File Access
- File Server: Storage growth reporting
- Licensing/Pricing
- Contact
Javascript must be enabled to download our products and perform other essential functions on the website.
IMPORTANT:
To try and make the filenames below a little easier to work with, they were changed in version 8.5. If you are using version 8.4 or older, click the Show Older Names button below to show the filenames that apply to your software version.
Show Newer Names Show Older Names
Documentation currently showing: Showing v8.4 and older filenames
File Type | New Name | Old Name |
---|---|---|
Private Key | SSL_PRIVATE_KEY.pem | CLIENT_PRIVATE.pem |
SSL Certificate | SSL_CERT.pem | SIGNED_CLIENT_CERT.pem |
Starting with version 9.4, you can optionally rename the two files above to something else to fit your process better. Set the new file names in the registry at:
HKEY_LOCAL_MACHINE\software\PAStorageMonitor
values SSL_CERT_NAME and SSL_PRIVATE_KEY_NAME
Those registry entries will need to be created, and they should only be set to the new filename, not the full path. For example:
SSL_CERT_NAME = myCert.pem
SSL_PRIVATE_KEY_NAME = myCert.key
To revert back to the old filenames, just delete those two registry entries. Any time these registry entries are changed, the monitoring service needs to be restarted.
PA Storage Monitor can use your own SSL certificate instead of the default self-signed certificate.
If at any time there are any problems with certificates, you can run the C:\Program Files\PA Storage Monitor\CA\000_RESET_CERTIFICATES.cmd file (run as an administrator), and then restart the service. New certificates will be created. If things are really messed up, you can delete the C:\Program Files\PA Storage Monitor\CA folder completely and restart the service to create a new CA folder.
Note that although the commands are shown on multiple lines, this is simply because there isn't space to show the full command one on line. But the text in the command boxes below should be run as a single command.
Sections of this document:
The conversion command:
current-pfx-password above is the current private key password for the .pfx file, and new-pem-password is the private key password for the output pem file.
Look at the resulting .pem file in a text editor -- you'll see there are two sections. Split this into two separate files, like below:
CLIENT_PRIVATE.pem file contents:You don't need the other lines that are in the file.
IMPORTANT: if your .pem file does not have a PRIVATE KEY section, then you must already have the private key in another file somewhere else - you must find that file and get it into pem format. The private key is created when the CSR (Certificate Signing Request) was initially sent to the certificate vendor (Verisign, GlobalSign, etc). It CANNOT be generated later - the private key and the certificate are a matched set.
If you want to include a full certificate chain in SIGNED_CLIENT_CERT.pem, make sure that:
Thank you Martin for these tips :)
If you want to include a full certificate chain in SIGNED_CLIENT_CERT.pem, make sure that:
Thank you Martin for these tips :)
Using ACME (Automatic Certificate Management Environment) is a great way to get real (not self-signed) certificates that can be automatically renewed and managed without needing manual steps. This is increasingly important as certificate expiration times keep getting shorter.
The win-acme client is an easy to use method of automating certificate management. The steps to use are outside of the scope of this document (see the win-acme website - it's well documented), but there are a few key steps for easy integration with PA Storage Monitor. You may need to create the certificate with "full options" to get to some of these options.
When asked about where to store the certificate it's important to choose PEM encoded files.
Choose to save the certificates in the PA Storage Monitor CA folder:
C:\Program Files\PA Storage Monitor\CA
Make sure to give the private key a password. You'll need it in a step below.
For this example, let's assume you created a certificate for www.myserver.com. You will end up with these files in the CA folder:
To tell PA Storage Monitor the name of the certificate and private key filename, use RegEdit to change the SSL_CERT_NAME and SSL_PRIVATE_KEY_NAME values under HKEY_LOCAL_MACHINE\software\PAStorageMonitor. Use the 'chain' and the private key filenames respectively.
Finally, tell PA Storage Monitor the private key password by running the following command:
You can now start/restart the PA Storage Monitor service and it will use your new certificate.
PA Storage MonitorName
|
|||||||||||||||||||||||||||||||