[
https://issues.apache.org/jira/browse/NIFI-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563899#comment-16563899
]
ASF GitHub Bot commented on NIFI-5473:
--------------------------------------
Github user andrewmlim commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2927#discussion_r206591826
--- Diff: nifi-docs/src/main/asciidoc/administration-guide.adoc ---
@@ -166,7 +166,7 @@ In order to facilitate the secure setup of NiFi, you
can use the `tls-toolkit` c
Wildcard certificates (i.e. two nodes `node1.nifi.apache.org` and
`node2.nifi.apache.org` being assigned the same certificate with a CN or SAN
entry of +*.nifi.apache.org+) are *not officially supported* and *not
recommended*. There are numerous disadvantages to using wildcard certificates,
and a cluster working with wildcard certificates has occurred in previous
versions out of lucky accidents, not intentional support. Wildcard SAN entries
are acceptable *if* each cert maintains an additional unique SAN entry and CN
entry.
-Potential issues with wildcard certificates:
+==== Potential issues with wildcard certificates:
--- End diff --
With the TOC Level Set to 3, should change this to:
Potential Issues with Wildcard Certificates
> Add documentation for using intermediate CA with TLS toolkit
> ------------------------------------------------------------
>
> Key: NIFI-5473
> URL: https://issues.apache.org/jira/browse/NIFI-5473
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website, Security, Tools and Build
> Affects Versions: 1.7.1
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Priority: Major
> Labels: certificate, documentation, security, tls, tls-toolkit
>
> With some manual work, the TLS toolkit can be used with a pre-existing
> certificate and private key that has been signed by an organization's
> certificate authority (CA) to sign toolkit-generated certificates. The Admin
> Guide should be improved to cover the necessary steps.
> When the separate "Security Guide" / "Toolkit Guide" is created, this content
> should be migrated there.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
