Thanks Bryan, I'd seen those properties, but had prematurely ruled them out them because 'input' was in the property name and I was wrestling with an 'output' port, but point taken. Setting them as you suggest does the trick as expected. Excellent!
I was also able to successfully sub-in the site-to-site client from 0.7.1 into a bundle based on flink 1.1.4 and get secure site-to-site to work perfectly. I had originally thought the version update wasn't going to work due to an errant NoClassDefFoundException, but it turned out to be a packaging problem. The mechanism for building a fat jar as demonstrated by the flink maven archetype needed some tweaking. Very much appreciate the nudge in the correct direction. Cheers, Drew On Wed, Jan 4, 2017 at 5:52 PM Bryan Bende <[email protected]> wrote: Hey Drew, For non-secure it should be able to see the output ports. I noticed that when I took a fresh 0.7.1 and didn't change any config, I did experience the behavior you described, but when I went to nifi.properties and set the following then it worked as expected: nifi.remote.input.socket.port=8088 nifi.remote.input.secure=false Basically in the 0.x line when the port is blank, site-to-site is disabled which is why don't see the ports. As far as Flink... we should definitely get the dependencies in Flink and Apex updated to a newer site-to-site client to benefit from these fixes that have been made. For now you can probably force your project to use a newer site-to-site client. I did something like this here where the project was using the Flink-NiFi connector from Flink 1.1.2, and then I was forcing the site-to-site client to NiFi 1.0.0: https://github.com/bbende/nifi-streaming-examples/blob/master/pom.xml#L22-L30 Thanks, Bryan On Wed, Jan 4, 2017 at 12:07 PM, Drew Farris <[email protected]> wrote: > Hi All, > > Is it possible for anonymous Site-to-Site clients to see Output Ports in > Non-Secure mode in 0.7.1? When I hit > http://localhost:8080/nifi-api/controller, no Output Ports are listed. > > I've verified that I can see Output Ports when running in secure mode, with > proper certificates and authorizations in place, etc. For my particular > use-case I'm running into NIFI-1907 because the Flink connector is still > dependent on the 0.6.1 artifacts which is a blocker. > > (I'm attempting to prove out a concept before I roll up my sleeves and > update the dependency in the Flink connector.) > > Drew >
