Many more examples throughout the documentation now use secure connections to servers.
Examples in the documentation use the hostname
localhost to contact local DS servers. Trust in the examples depends on the use of a deployment key and password when setting up servers. A server certificate generated from a deployment key and password has
localhost as the default hostname. By using the
--hostname localhost option with a DS command-line tool, you simplify the secure connection process. When the tool validates the specified hostname against the hostname in the server certificate, they match. There is no need to add the server's hostname to the server certificate.
When making a secure connection to a remote server, be sure the FQDN in the
--hostname fqdn option matches a valid hostname in the server certificate. If the server certificate is generated with a deployment key and password, you can easily renew the certificate to change or add a hostname. For examples, see "Replace a TLS Key Pair" or "Generate a Key Pair (Wildcard Certificate)".
Adapt the examples as necessary when using your own certificates, keys, and PKI.