update notice on self signed for kafka and fluentd

This commit is contained in:
Denise Schannon
2019-03-23 23:54:19 -07:00
parent 2cdcfb4e84
commit d923ea73d3
2 changed files with 5 additions and 9 deletions
@@ -29,4 +29,6 @@ After adding all the Fluentd servers, you have the option to select **Enable Gzi
## SSL Configuration
If your Fluentd servers are using TLS, you need to select **Use TLS**. If you are using a self-signed certificate, provide the **CA Certificate PEM**. You can copy and paste the certificate or upload it using the **Read from a file** button.
If your Fluentd servers are using TLS, you need to select **Use TLS**. Provide the **CA Certificate PEM**. You can copy and paste the certificate or upload it using the **Read from a file** button.
>**Note:** Fluentd does not support self signed certificates.
@@ -26,15 +26,9 @@ If your Kafka cluster is using SSL for the **Broker**, you need to complete the
1. Provide the **Client Private Key** and **Client Certificate**. You can either copy and paste them or upload them by using the **Read from a file** button.
- You can use either a self-signed certificate or one provided by a certificate authority.
1. Provide the **CA Certificate PEM**. You can either copy and paste the certificate or upload it using the **Read from a file** button.
- You can generate a self-signed certificate using an openssl command. For example:
```
openssl req -x509 -newkey rsa:2048 -keyout myservice.key -out myservice.cert -days 365 -nodes -subj "/CN=myservice.example.com"
```
1. If you are using a self-signed certificate, provide the **CA Certificate PEM**. You can either copy and paste the certificate or upload it using the **Read from a file** button.
>**Note:** Kafka does not support self signed certificates.
### SASL configuration