Hi Chien,
Thanks for providing the additional configuration info.
> nifi.remote.input.host and nifi.remote.input.socket.port is different for
> each node. If the remote process group url doesn't have to point to the ncm
> anymore, is it recommended to use a vip or dns rr alias?
No, vip or dns
I'm using NiFi for a very simple, yet non-standard way - as a POC scheduler to
call an existing stored procedure using an ExecuteSQL processor. The processor
is timer driven (every 4 hours), uses a basic JDBC connection, and executes a
stored procedure call that contains one hard-coded variable.
Hi Koji,
The remote process group is configured as follows:
URL - http://host02.corp:1/nifi
Transport Protocol - RAW
Communications Timeout - 30 sec
Yield Duration - 10 sec
Proxy settings are all blank.
nifi.remote properties:
# Site to Site properties
nifi.remote.input.host=host02.corp
nif
Peter has found and corrected our issue.
When setting up our truststore we failed to include the cert for the root CA.
We only included the certs for the individual hosts running NiFi. This left us
in a half-functional state where we could create a secure connection for
site-to-site but all t
Thanks Kawamura-san.
-Original Message-
From: Koji Kawamura [mailto:ijokaruma...@gmail.com]
Sent: Monday, September 12, 2016 2:08 AM
To: users@nifi.apache.org
Subject: Re: Interesting Site-to-Site quirk with
nifi.security.identity.mapping.pattern.dn
Hello Peter,
Thanks for reporting th
Hello Peter,
Thanks for reporting this! I agree with you and feel this needs to be
fixed. I'm going to work on this.
Koji
On Mon, Sep 12, 2016 at 12:41 PM, Peter Wicks (pwicks)
wrote:
> I’ve been playing with site-to-site and found an interesting quirk. I had
> the full DN’s from my certificat
