Hello Kumiko,
Sorry to hear that you're having issues with upgrading to 1.0.0.
1) Any NiFi API URL of a node in the remote cluster should work for
the target URL. If there're node1, 2, 3 in a remote cluster then
"http://node<1, 2 or 3>:/nifi" should work. Every node is
capable to handle web reque
I've been playing with site-to-site and found an interesting quirk. I had the
full DN's from my certificates for my usernames, but decided to setup
nifi.security.identity.mapping patterns for both the DN's and for Kerberos;
which by the way works great for normal users.
I renamed just my own a
