[
https://issues.apache.org/jira/browse/NIFI-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886037#comment-15886037
]
ASF GitHub Bot commented on NIFI-3490:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1530
In general I would push to keep the flags consistent across client/server
and standalone mode. On the other hand, I am hesitant to change a flag that
already exists in the wild (although, it was just committed to master; it's not
in a release yet).
I guess talking through that to myself, I would vote for "change the
client/server flag to be consistent with standalone" but I would also welcome
input from @brosander and @joewitt .
> TLS Toolkit - define SAN in standalone mode
> -------------------------------------------
>
> Key: NIFI-3490
> URL: https://issues.apache.org/jira/browse/NIFI-3490
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Minor
> Labels: tls-toolkit
> Fix For: 1.2.0
>
>
> Following NIFI-3331, it would be useful to have the same option (add Subject
> Alternative Names in certificates) when using the TLS toolkit in standalone
> mode.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
