Also one more note, if you want to add that same debugging on the NiFi or NiFi Registry side then it would go in the bootstrap.conf as a java.arg like:
java.arg.17=-Djavax.net.debug=ssl:handshake Then restart the application and the SSL handshake debug should go to nifi-boostrap.log, or nifi-registry-bootstrap.log On Wed, Oct 24, 2018 at 5:24 PM Bryan Bende <[email protected]> wrote: > > Can you try editing cli.sh and near the end where it actually executes > the CLIMain, edit the line to add the -D for SSL handshake debugging > so it looks like this: > > exec "${JAVA}" -cp "${CLASSPATH}" ${JAVA_OPTS:--Xms128m -Xmx256m} > -Djavax.net.debug=ssl:handshake org.apache.nifi.toolkit.cli.CLIMain > "$@" > > Then run your command and you should see all the debugging info print > out to the console. Curious to see what that shows. > On Wed, Oct 24, 2018 at 5:03 PM ara m. <[email protected]> wrote: > > > > I tried the ssldump tool, didnt have much luck with it no matter which > > parameters i passed in. Not sure if its because my cluster everything is > > dockerized and hides the communication so it cannot parse the communication > > then. > > > > Still stuck without being able to use CLI from inside NiFi container using > > NiFi keystore+truststore.. > > > > > > > > -- > > Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
