Hi Mike, Thanks for your response. I think, there are some changes happened in NiFi 1.8 around this, the earlier version (NiFi 1.7) was just worked fine with IBM JDK.
Regards, Dnyaneshwar Pawar From: Mike Thomsen <[email protected]> Sent: Thursday, January 17, 2019 5:33 PM To: [email protected] Subject: Re: Exception when setting up NiFi 1.8 with IBM JDK (SSL Setup). This is something that we could write a Jira ticket against, but as it is hard-coded for now, I don't think there's a work around. On Thu, Jan 17, 2019 at 6:57 AM Dnyaneshwar Pawar <[email protected]<mailto:[email protected]>> wrote: …just found out that Jetty is not loading appropriate keystore provider for IBM JDK which should be IBMJCE. It is always returning SUN. Any pointers? Regards, Dnyaneshwar Pawar From: Dnyaneshwar Pawar Sent: Friday, December 21, 2018 3:00 PM To: [email protected]<mailto:[email protected]> Subject: Exception when setting up NiFi 1.8 with IBM JDK (SSL Setup). Hi, As a upgrade process we tried using NiFi 1.8(HTTPS) with IBM JDK 1.8, PFB screenshot of the actual java -version command. [cid:[email protected]] Below is the screen capture of error occurred while trying to start nifi: [cid:[email protected]] [cid:[email protected]] We have tried couple of way such as setting JCE provider, generating keystore with IBM keytool, nothing helped. The same IBM JDK and NiFi 1.7combination just works fine. Just checked KeystoreUtils file and it seems provider for JKS type is SUN, then why it fails to load the keystore? Regards, Dnyaneshwar Pawar DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.
