[
https://issues.apache.org/jira/browse/NIFI-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879303#comment-15879303
]
ASF GitHub Bot commented on NIFI-3490:
--------------------------------------
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/1530
Test example:
````
./tls-toolkit.sh standalone -s "nifi.vip.org,localhost,nifi-01" -n nifi-01
````
````
$ keytool -list -keystore keystore.jks -v
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 1 entry
Alias name: nifi-key
Creation date: Feb 22, 2017
Entry type: PrivateKeyEntry
Certificate chain length: 2
Certificate[1]:
Owner: CN=nifi-01, OU=NIFI
Issuer: CN=localhost, OU=NIFI
Valid from: Wed Feb 22 22:25:30 CET 2017 until: Sat Feb 22 22:25:30 CET 2020
Certificate fingerprints:
...
Extensions:
#1: ObjectId: 2.5.29.35 Criticality=false
...
#2: ObjectId: 2.5.29.19 Criticality=false
...
#3: ObjectId: 2.5.29.37 Criticality=false
...
#4: ObjectId: 2.5.29.15 Criticality=true
...
#5: ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
DNSName: nifi.vip.org
DNSName: localhost
DNSName: nifi-01
]
#6: ObjectId: 2.5.29.14 Criticality=false
...
````
> 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
>
> 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)
