[
https://issues.apache.org/jira/browse/NIFI-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886135#comment-15886135
]
ASF GitHub Bot commented on NIFI-3490:
--------------------------------------
Github user brosander commented on the issue:
https://github.com/apache/nifi/pull/1530
I agree that changing flags is likely to cause confusion although since we
haven't had a release yet, I would hope it would be minimal impact. Consistency
across modes of operation will help reduce surprise which is always a good
thing.
Do we expect this to be something most users specify or is it a more
advanced usecase? If it's more advanced and less common then a short version
of the argument may not be necessary.
> 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)
