[
https://issues.apache.org/jira/browse/NIFI-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15625432#comment-15625432
]
Aldrin Piri commented on NIFI-2974:
-----------------------------------
Aren't the TLS toolkit certificates primarily tailored toward intra-NiFi
communications?
I would have concerns this could be confusing for users whom typically use
SSLContextService for communicating with external sites and services. This has
come up in discussion a few times across the various mailing lists in terms of
trying to help folks have things that just work a bit more so.
One example is:
http://apache-nifi.1125220.n5.nabble.com/Nifi-GetHttp-https-endpoint-keystore-password-error-td1216.html
We had a bit of discussion surrounding ways we might be a bit smarter for
handling this throughout environments but couldn't come to a consensus on a
consistent solution. My mailing list searching skills fail me to find that
chain.
> Populate default values in SSLContextService creation dialog
> ------------------------------------------------------------
>
> Key: NIFI-2974
> URL: https://issues.apache.org/jira/browse/NIFI-2974
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Affects Versions: 1.0.0
> Reporter: Andy LoPresto
> Priority: Trivial
> Labels: beginner, tls, ui
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> When users create a {{SSLContextService}}, some common default values could
> be auto-populated:
> * {{Keystore location}} - {{$NIFI_HOME/conf/keystore.jks}}
> * {{Keystore Type}} - {{JKS}}
> * {{Truststore location}} - {{$NIFI_HOME/conf/truststore.jks}}
> * {{Truststore Type}} - {{JKS}}
> These are the default values when using the TLS Toolkit and safe defaults for
> manual generation as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
