Created 01-21-2022 08:36 AM
We're trying to upgrade from TLSv1.0 to TLSv1.2 for the below configuration but getting error as attached.
These are the installed versions
HDF: 3.1.0
Nifi: 1.5.0.3.1.0.0-564
Ambari: 2.6.2.2
HDP: 2.6.5.1100.
we have tried following the steps from this page and it didn't worked as well.
https://community.cloudera.com/t5/Support-Questions/Nifi-SSL-TLS-qestion/td-p/285528
Kindly help me to resolve this issue.
Created 01-25-2022 12:53 PM
You are running in to a known bug in that version of Apache NiFi. The bug was addressed in Apache NiFi 1.14. Upgrading Apache NiFi 1.5 to 1.14 would solve the issue for you.
Here are the bugs that addressed the issue:
https://issues.apache.org/jira/browse/NIFI-8281
https://issues.apache.org/jira/browse/NIFI-8630
If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post.
Thank you,
Matt
Created 01-24-2022 09:08 AM
$JAVA_HOME/jre/lib/security/java.security
jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, SSLv2Hello, RC4, DES, MD5withRSA, \
DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \
include jdk.disabled.namedCurves
Is there a way to restrict PutEmail Processor to use TLSv1.2 while sending request to SMTP server?
Created 01-25-2022 12:53 PM
You are running in to a known bug in that version of Apache NiFi. The bug was addressed in Apache NiFi 1.14. Upgrading Apache NiFi 1.5 to 1.14 would solve the issue for you.
Here are the bugs that addressed the issue:
https://issues.apache.org/jira/browse/NIFI-8281
https://issues.apache.org/jira/browse/NIFI-8630
If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post.
Thank you,
Matt
Created on 01-31-2022 08:33 AM - edited 01-31-2022 08:41 AM
Can we upgrade HDF 3.1.0 directly to 3.5 without upgrading Amabri and HDP? and if not, is there any document guiding how we can upgrade from HDF 3.1.0 to HDF 3.5.
Created 01-31-2022 02:05 PM
This question is not related to the original question in this post. I recommend starting a new question, so as to avoid confusion via a new conversation when this post already has an accepted solution.
Thanks,
Matt