Customer-Supplied Certificates for Control Station
To satisfy more stringent requirements, VNX users are allowed to install and configure their own X.509 certificate on the Control Station for HTTPS communication.
The form and content of customer-supplied X.509 certificates are up to the users. The certificate should be PEM-encoded and should not have an associated password. Otherwise, the Apache web server will not be able to start unattended which will interfere with failover and restart operations.
The customer-supplied private key should be copied to the directory
/nas/http/conf/ssl.key and the certificate should be copied to
/nas/http/conf/ssl.crt to avoid potential data loss after failover. When the new private key and certificate are in place, make sure the current key and certificate in the directory
/nas/http/conf are updated to point to the newly installed private key and certificate, respectively.
NOTE:The private key must be owned by user root and have permissions set to 600 (-rw-------). The public certificate also needs to be owned by user root, but have permissions set to 644 (-rw-r--r--).
NOTE:You can verify the new server certificate by viewing the characteristics of the HTTPS connection after pointing the supported web browser to the Control Station.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\