Secure daemon communication using HTTPS
Contributors
Suggest changes
-
PDF of this doc site
-
Administration for Linux
- Role-based access control in SnapDrive for UNIX
-
Installation and Administration for Solaris
- Role-based access control in SnapDrive for UNIX
- Creating and using Snapshot copies in SnapDrive for UNIX
-
Installation and Administration for IBM AIX
- Role-based access control in SnapDrive for UNIX
-
Administration for Linux
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
You can use HTTPS for secure Web services and daemon communication. Secure communication is enabled by setting some configuration variables in the snapdrive.conf
file, and generating and installing the self-signed or CA-signed certificate.
You must provide the self-signed or CA-signed certificate at the path specified in the snapdrive.conf
file. To use HTTPS for communication, you must set the following parameters in the snapdrive.conf
file:
-
use-https-to-sdu-daemon=on
-
contact-https-port-sdu-daemon=4095
-
sdu-daemon-certificate-path=/opt/NetApp/snapdrive/snapdrive.pem
SnapDrive 5.0 for UNIX and later versions support HTTPS for daemon communication. By default, the option is set to off .
|