[ https://issues.apache.org/jira/browse/NIFI-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608552#comment-15608552 ]
Bryan Rosander commented on NIFI-2943: -------------------------------------- [~alopresto] I agree that the tls-toolkit should default to JKS for keystores but currently the PKCS12 keystore functionality is useful for giving the user something they can immediately import into their browser. I think we should keep the option there for that reason but make it more explicit that that is the intended purpose. > tls-toolkit pkcs12 truststore 0 entries > --------------------------------------- > > Key: NIFI-2943 > URL: https://issues.apache.org/jira/browse/NIFI-2943 > Project: Apache NiFi > Issue Type: Bug > Reporter: Bryan Rosander > Assignee: Bryan Rosander > Priority: Minor > > When pkcs12 is used by the tls-toolkit, the resulting truststore has no > entries when inspected by the keytool and the tls-toolkit certificate > authority certificate is not trusted by NiFi. > This seems to be due to the Java pkcs12 provider not supporting certificate > entries: > http://stackoverflow.com/questions/3614239/pkcs12-java-keystore-from-ca-and-user-certificate-in-java#answer-3614405 > The Bouncy Castle provider does seem to support certificates but we may not > want to explicitly use that provider from within NiFi. -- This message was sent by Atlassian JIRA (v6.3.4#6332)