Hey Robert, If everything else fails, you might want to try out https://github.com/adamdebreceni/c2-server (note: I'm a contributor to that project) it's a new open source (apache 2 licensed) C2 server that helps with design, deployment and monitoring via webui for both minifi java and minifi c++.
On Thu, Jan 16, 2025 at 7:20 AM Robert Cohen <robert.co...@anu.edu.au.invalid> wrote: > > Ive tried running the transform-yml. The output appears to be minifi > json. Not nifi json. > > So I think that doco is misleading. > > > The code exported as a template from niifi 1.28.1, converted to a minifi > 1.28.1 yml then converted to a minifi 2.1.0 json appears to work. > > Wheres the same code exported from nifi 2.1.0 and converted to minifi > json doesnt. > > I'll start comparing the two and see if I can spot the problem. > > > > On 16/1/2025 4:00 pm, Robert Cohen wrote: > > > > Im coming at it a different way. Im trying to take the code from > > minifi 1.28.1 and convert it to minifi 2.1.0. > > > > > > Now the minifi toolkit 2.1.0 help says > > > > Valid commands include: > > transform-nifi: Transform NiFi flow JSON format into MiNifi flow JSON > > format > > transform-yml: Transform MiNiFi config YAML into NiFi flow JSON format > > > > So does that mean I need to use transform-yml to convert it to nifi > > flow format. > > > > Then use transform-nifi to convert it from nifi flow format to minifi > > flow format > > > > > > On 14/1/2025 9:25 pm, Robert Cohen wrote: > >> No, the TLS keystore and truststores are all set up. > >> And everything works fine in the original nifi sender. > >> Its only when I copy the code from the original nifi sending host to > >> either a minifi or another nifi, that things stop working. > >> > >> On 14/01/2025 5:07 pm, Matthew Hawkins wrote: > >>> [You don't often get email from hawko2...@gmail.com. Learn why this > >>> is important at https://aka.ms/LearnAboutSenderIdentification ] > >>> > >>> Hi Robert, > >>> > >>> You mentioned you have not setup the TLS side. From about Nifi 1.17 > >>> or so, > >>> this has been the default and expected behavior. > >>> > >>> Please setup the Nifi instance properly with TLS certs (they can be > >>> self > >>> signed, I have a script on GitHub gist to help with this previously > >>> shared > >>> with this forum). > >>> > >>> You drop the other side's client certificate into trusted keystore and > >>> setup an association via the SSLContextService associated with the RPG. > >>> > >>> There's not a lot of logging available when this fails, but having > >>> done it > >>> several times with third party REST interconnects and Nifi to Nifi I > >>> can > >>> assure you there's something in the code since back then that just > >>> won't > >>> let unencrypted unauthenticated sessions transmit. As a security > >>> professional, I like it fails (but dislike it fails silently or > >>> weirdly). > >>> > >>> Kind regards, > >>> > >>> On Tue, 14 Jan 2025, 16:23 Robert Cohen, > >>> <robert.co...@anu.edu.au.invalid> > >>> wrote: > >>> > >>>> Ive got no idea whats going on with this thing. > >>>> > >>>> I thought it might have been a minifi issue or a converter issue, > >>>> so Im > >>>> trying to export a process group from my source nifi and push it > >>>> into > >>>> another standalone nifi. > >>>> > >>>> Since I dont care about the GUI, I havent bothered to set up > >>>> authentication or authorization. > >>>> > >>>> I just took the the exported flow definition and renamed it to > >>>> flow.json.raw > >>>> > >>>> But the code doesnt appear to be running properly in the standalone > >>>> nifi > >>>> either. > >>>> > >>>> The app log doesnt show anything. Just the regular checkpoints. > >>>> > >>>> None of the processors or the RPG appear to be running. > >>>> > >>>> I'll have to try and get the GUI working so I can log into it and see > >>>> whats going on. > >>>> > >>>> > >>>> > >>>> On 13/1/2025 1:21 pm, Robert Cohen wrote: > >>>>> Yes, Ive checked the logs. > >>>>> > >>>>> There are no error messages of any kind or any indication that its > >>>>> attempting to transmit anything at all. > >>>>> > >>>>> Its as if the remote process group is either disconnected or > >>>>> disabled. > >>>>> > >>>>> > >>>>> The nifi URL works when its in the originating source nifi. And Im > >>>>> running the minifi on the same host as the source nifi. So things > >>>>> like > >>>>> firewalls/routing arent an issue. > >>>>> > >>>>> And https:odc-nifi-test.nci.org.au:444/nifi is the correct URL for > >>>>> the > >>>>> destination remote NIFI. > >>>>> > >>>>> Im going to try a flow file converted from the minifi 1 > >>>>> config.ynl, If > >>>>> that works I;ll have sonething to compare. > >>>>> > >>>>> I'll also try importing the exported flow into a new NIFI and see if > >>>>> theres something wrong with the exported file. > >>>>> > >>>>> > >>>>> On 10/1/2025 8:49 pm, Kedvessy Péter wrote: > >>>>>> [You don't often get email frompkedve...@gmail.com. Learn why > >>>>>> this is > >>>>>> important athttps://aka.ms/LearnAboutSenderIdentification ] > >>>>>> > >>>>>> Hi Robert, > >>>>>> > >>>>>> Have you checked your minifi agent logs? Specifically the > >>>>>> minifi-app.log. > >>>>>> There should be an error describing the reason for the failed > >>>>>> connection/communication with the remote NiFi instance... Is > >>>>>> https:odc-nifi-test.nci.org.au:444/nifi the right URI of your remote > >>>>>> NiFi > >>>>>> instance where you are expecting flow files from the minifi agent? > >>>>>> > >>>>>> Regards, > >>>>>> Peter > >>>>>> > >>
