Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Use warning block in TLS recommendation 

Other minor edits
pull/533/head
pierwill 2019-10-21 10:17:39 -07:00
parent 3138ab52fc
commit fd5602e564
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/v2.0/security/https_setup.md
View File

@ -7,13 +7,15 @@ menu:
v2_0: v2_0:
name: Enabling HTTPS name: Enabling HTTPS
parent: Security & authorization parent: Security & authorization
v2.0/tags: [security, authentication, tls] v2.0/tags: [security, authentication, tls, https]
--- ---
Enabling HTTPS encrypts the communication between clients and the InfluxDB server. Enabling HTTPS encrypts the communication between clients and the InfluxDB server.
When configured with a signed certificate, HTTPS can also verify the authenticity of the InfluxDB server to connecting clients. When configured with a signed certificate, HTTPS can also verify the authenticity of the InfluxDB server to connecting clients.
{{% warn %}}
InfluxData [strongly recommends](/influxdb/v1.7/administration/security/) enabling HTTPS, especially if you plan on sending requests to InfluxDB over a network. InfluxData [strongly recommends](/influxdb/v1.7/administration/security/) enabling HTTPS, especially if you plan on sending requests to InfluxDB over a network.
{{% /warn %}}
## Requirements ## Requirements
@ -35,10 +37,10 @@ InfluxDB supports three types of TLS certificates:
* **Self-signed certificates** * **Self-signed certificates**
Self-signed certificates are _not_ signed by a Certificate Authority (CA). Self-signed certificates are _not_ signed by a Certificate Authority (CA).
[Generate a self-signed certificate]((#step-1-generate-a-self-signed-certificate)) on your own machine.
Unlike CA-signed certificates, self-signed certificates only provide cryptographic security to HTTPS requests. Unlike CA-signed certificates, self-signed certificates only provide cryptographic security to HTTPS requests.
They do not allow clients to verify the identity of the InfluxDB server. They do not allow clients to verify the identity of the InfluxDB server.
With this certificate option, every InfluxDB instance requires a unique self-signed certificate. With this certificate option, every InfluxDB instance requires a unique self-signed certificate.
You can generate a self-signed certificate on your own machine.
<!-- InfluxDB supports certificates composed of a private key file (`.key`) and a signed certificate file (`.crt`) file pair, --> <!-- InfluxDB supports certificates composed of a private key file (`.key`) and a signed certificate file (`.crt`) file pair, -->
<!-- as well as certificates that combine the private key file and the signed certificate file into a single bundled file (`.pem`). --> <!-- as well as certificates that combine the private key file and the signed certificate file into a single bundled file (`.pem`). -->