Hi Phil,
One thing I notice with your config is that the cluster.node.protol.port and
the zookeeper ports are the same - these should not be the same.
Node.protocol.port is used by NiFi cluster to communicate between nodes, the
zookeeper.connect.string port should be the port that zookeeper ser
va:375)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at org.apache.zookeeper.server.quorum.Leader.(Leader.java:193)
at
org.apache.zookeeper.server.quorum.QuorumPeer.makeLeader(QuorumPeer.java:605)
at
org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:79
nifi2/conf/nifi.properties:nifi.state.management.embedded.zookeeper.start=false
nifi2/conf/zookeeper.properties not required
Nathan
On 10/2/18, 11:25 AM, "Nathan Gough" wrote:
Check your configs on nifi2. I don't believe that NiFi is starting two
instances of Zookeeper but
nfig has been a mystery to me. I
thought it was a second port used for elections, not the upper bound in a
range. Why is the range so large?
Sent from Mail for Windows 10
From: Nathan Gough
Sent: Wednesday, 3 October 2018 1:26 AM
To: dev@nifi.apache.org
Subject: Re: Z
Hi Mike,
Sure I can look at fixing up PR-2977 today.
Nathan
On 10/16/18, 6:13 AM, "Mike Thomsen" wrote:
Does 5562 need to be addressed in 1.8?
https://github.com/apache/nifi/pull/2977
On Mon, Oct 15, 2018 at 6:33 PM Jeff wrote:
> NiFi Devs,
>
> The Rel
me to upgrade and test.
Nathan
On 10/16/18, 10:58 AM, "Nathan Gough" wrote:
Hi Mike,
Sure I can look at fixing up PR-2977 today.
Nathan
On 10/16/18, 6:13 AM, "Mike Thomsen" wrote:
Does 5562 need to be addressed in 1.8?
+1
Verified signatures and hashes.
Built from source and tested my changes for the release.
Checked the README/NOTICE/LICENSE files
On 10/19/18, 7:23 AM, "Marc Parisi" wrote:
+1 binding
Did the usual release helper validation, tested with typical use cases
and test flows, with a
-1 (revote)
On further testing I have found that the SSLContextService does not work as
expected due to this ticket https://jira.apache.org/jira/browse/NIFI-4558 and
the related PR. This makes it difficult or impossible to use the
SSLContextService as I believe the customValidate() method takes
+1 (non-binding)
- Verified signature
- Verified checksums
- mvn contrib executed successfully
- Created simple test flow in both standalone and clustered modes, secure
and insecure
- Checked license and readme files
Nathan
On Wed, Mar 13, 2019 at 6:33 PM Arpad Boda wrote:
> +1
>
> -Verified
Apache NiFi Community,
The https://nifi.apache.org/security.html page has been updated with 3
vulnerabilities discovered in previous NiFi versions which have been
resolved in release 1.10.0. The severity of these were determined to be two
'low' and one 'medium'. Dependency vulnerabilities that wer
Hi Mark,
The minimum version for an external zookeeper should be 3.5.5. Are you
experiencing any issues?
Nathan
On Fri, Nov 22, 2019 at 3:30 PM Mark Bean wrote:
> For NiFi 1.10.0, what is the minimum version of zookeeper when using an
> external zookeeper instance?
>
> Thanks,
> Mark
>
Hi Uma,
Attached images do not come through to mailing lists. You will need to
post the error as text or send a URL to the image.
Nathan
On Mon, Nov 25, 2019 at 10:39 AM Umasri Vullanki
wrote:
> Hi Team,
>
> For secure cluster setup,
>
> -> Initially created a 2-node cluster with all the confi
+1 non-binding
Verified hashes, signing key, did a 'mvn clean install
-Pcontrib-check,include-grpc' and ran a secured NiFi cluster with the
resulting bin.
Nathan
On Wed, Jan 22, 2020 at 11:51 AM Shawn Weeks
wrote:
> +1 non-binding
>
> On 1/22/20, 10:48 AM, "Shawn Weeks" wrote:
>
> Notice
Apache NiFi Community,
The https://nifi.apache.org/security.html page has been updated with 2
vulnerabilities discovered in previous NiFi versions which have been
resolved in release 1.11.0. The severity of these were determined to be one
'high' and one 'moderate'. Dependency vulnerabilities that
Hi Joe,
I just set up a secure cluster with NiFi 1.11.3 and am not seeing any
issues like you describe.
Are you running Java 8 or Java 11?
Nathan
On Wed, Feb 26, 2020 at 12:22 PM Joe Gresock wrote:
> Were there any changes with how the trust store is used in 1.11.3? I had a
> 1.11.0 deployme
Hi Joe,
Just to confirm here - was the nifi.security.keyPasswd not defined at all
in your nifi.properties? Did you have to add the property and give it the
correct value? Or was it in the nifi.properties file but blank? Or were the
keyPasswd and keystorePasswd different values?
Thanks,
Nathan
On
I've opened https://issues.apache.org/jira/browse/NIFI-7223 to track and
I'm working on a fix for this.
Nathan
On Tue, Mar 3, 2020 at 6:17 PM Nathan Gough wrote:
> Hi Joe,
>
> Just to confirm here - was the nifi.security.keyPasswd not defined at all
> in your nifi.prope
+1 (non-binding)
Built with tests, connected a secured nifi to a secured registry. Connected
NiFi LDAP, logged in and out with LDAP and tested API to confirm the token
is invalidated as expected. Version controlled a simple flow.
On Thu, Apr 2, 2020 at 4:09 PM Aldrin Piri wrote:
> I am of the o
Hi Midhun,
We probably need more logs than that. I think there can be a few reasons
why you're seeing that error. Please provide logs immediately following the
failed replicate request.
Thanks,
Nathan
On Sun, Oct 4, 2020 at 7:16 AM Midhun Mohan wrote:
> Hi Team,
>
> When I tried setting up a s
If possible I would like to get
https://issues.apache.org/jira/browse/NIFI-7356 in for this release as
well. This enables TLS + embedded Zookeeper. Right now, the PR for TLS +
external Zookeeper is merged, and there is an open PR for TLS + embedded
Zookeeper here: https://github.com/apache/nifi/pul
+1 non-binding from me.
Ran through the release helper and set up a secure cluster with a secure
embedded ZooKeeper, a simpler secure cluster without secured ZK, and a
secure cluster with secure external ZK.
On Fri, Jan 29, 2021 at 12:46 PM Matt Burgess wrote:
> +1 Release this package as nifi-
+1 (non-binding)
- Verified signature and checksums again
- Ran build with
java -version
openjdk version "1.8.0_282"
OpenJDK Runtime Environment (Zulu 8.52.0.23-CA-macosx) (build 1.8.0_282-b08)
OpenJDK 64-Bit Server VM (Zulu 8.52.0.23-CA-macosx) (build 25.282-b08,
mixed mode)
- Tested secure c
I 100% agree that something needs to be done. We cannot allow NiFi to build
a reputation that it is 'insecure' by allowing its default installation to
start up without any security. Especially considering how much work we put
in to make sure it IS a secure product that integrates with many
applicat
+1 (non-binding)
Verified release signatures, built and ran a secure cluster with secure
embedded ZK. Tested some network based processors on the canvas.
Cheers,
Nathan
On Sat, Mar 13, 2021 at 10:50 AM Pierre Villard
wrote:
> +1 (binding)
>
> Went through the usual steps, checked a set of flow
Congratulations Joey! Thanks for your past and future contributions.
On Thu, Mar 25, 2021 at 3:15 PM Joey Frazee
wrote:
> I want to make sure to say thanks for the recognition! I’m thrilled to be
> a part of this. The help and collaboration from the project members and
> contributors over the pa
Joe Gresock just pinged me about an issue that may have been introduced by
a dependency upgrade I did for lucene:
https://issues.apache.org/jira/browse/NIFI-8699 which appears to cause an
issue for existing provenance repositories. I tested the upgrade on a fresh
install so I didn't notice the issu
+1 (non-binding)
- Built from source + test, checked hashes
- Ran with a secure three node cluster and X509 authentication, tested S2S
and some other processors
- Ran single secure node with OIDC authentication (G Suite)
- Ran single secure node with SAML authentication (G Suite)
java -version
o
I'm a +1 for removing pretty much all of this stuff. There are security
implications to keeping old dependencies around, so the more old code we
can remove the better. I agree that eventually we need to move to
supporting only Java 11+, and as our next release will probably be about 4
- 6 months fr
Hi Firdous,
Can you give us more details about what issue you're facing? Error
logs/config files? Are you trying to use client certificate authentication
as well or some other authentication?
Thanks,
Nathan
On Thu, Nov 11, 2021, 7:38 PM Firdous Fatima
wrote:
> Good evening,
>
> Hope you’re doi
Little bit late but +1 non binding, verified the hashes and tested a secure
cluster + secure external ZK and some data flows.
On Wed, Dec 15, 2021 at 2:31 PM Joe Witt wrote:
> Apache NiFi Community,
>
> I am pleased to announce that the 1.15.1 release of Apache NiFi passes with
> 6 +1 (bindi
Congrats Margot, thanks for all your contributions!
On Wed, Dec 15, 2021 at 3:02 PM Chris Sampson
wrote:
> Congrat Margot!
>
> ---
> *Chris Sampson*
> IT Consultant
> chris.samp...@naimuri.com
>
>
> On Wed, 15 Dec 2021 at 19:04, Pierre Villard
> wrote:
>
> > Congrats Margot!
> >
> > Le mer. 15
Severity: Low
Description:
In the TransformXML processor an authenticated user could configure an
XSLT file which, if it included malicious external entity calls, may
reveal sensitive information.
This issue is being tracked as NIFI-9399
Credit:
This issue was discovered by DangKhai at Viettel
[1] https://issues.apache.org/jira/browse/NIFI-9642 <
> https://issues.apache.org/jira/browse/NIFI-9642>
> [2] https://issues.apache.org/jira/browse/NIFI-7339 <
> https://issues.apache.org/jira/browse/NIFI-7339>
>
>
> > On Jan 28, 2022, at 7:56 AM, Nathan Gough wro
ore 12:17 Jordan Zimmerman
> > ha scritto:
> > >
> > > I don't have the bandwidth currently unfortunately.
> > >
> > > -Jordan
> > >
> > > > On Feb 7, 2022, at 7:31 PM, Enrico Olivelli
> > wrote:
> > > >
> &g
I also ran into both of these issues. Though it was just a me problem.
The value in my build.properties is:
Build-Timestamp:${timestamp}
On Fri, Mar 11, 2022 at 6:03 PM Bryan Bende wrote:
> Mike,
>
> What is the value of timestamp in your
> nifi-manifest/nifi-runtime-manifest/target/classes/bui
Congrats, Paul! Thanks for your contributions so far.
On Wed, Mar 16, 2022 at 9:06 PM Marton Szasz wrote:
> Congratulations, Paul!
>
> On Thu, 17 Mar 2022 at 00:00, Joe Witt wrote:
> >
> > Congrats and thanks!
> >
> > On Wed, Mar 16, 2022 at 4:55 PM gre...@yahoo.com.INVALID
> > wrote:
> >
> >
+1 (non-binding), looks good to me.
Ran through the release helper, tested a few flows, tested a secure cluster
with external ZK, and tested OIDC auth.
On Tue, Mar 22, 2022 at 5:59 PM Matt Burgess wrote:
> +1 Release this package as nifi-1.16.0
>
> Ran through release helper, ran a couple flows
Severity: moderate
Description:
When creating or updating credentials for single-user access, NiFi
wrote a copy of the Login Identity Providers configuration to the
operating system temporary directory. On most platforms, the operating
system temporary directory has global read permissions. NiFi
+1 (non-binding), ran a 3 node cluster using external ZK with some simple
test flows. Ran NiFi with Google OIDC auth. Checked hashes and other files.
On Wed, Apr 27, 2022 at 10:24 AM Mike Thomsen
wrote:
> +1 (binding) Ran a simple tika extraction flow on PDFs and DOCX files.
> Worked fine. Saved
+1 (non-binding)
Tested out 3 node secure cluster and external ZK with a few different
processors, set up and tested Google OIDC authentication.
Nathan
On Tue, May 24, 2022 at 5:54 PM Mark Payne wrote:
> +1 (binding)
>
> Performed build with Java 8.
> Ran with Java 8 and Java 11.
> Tested inse
+1 (non-binding)
Ran a 3 node cluster with external Zookeeper, ran some test flows.
Thanks!
Nathan
On Tue, Jun 14, 2022 at 12:31 PM David Handermann <
exceptionfact...@apache.org> wrote:
> +1 (binding)
>
> - Verified signatures and hashes
> - Ran build using Maven 3.8.5
> - Ran build on Ubuntu
- Tested OIDC with G Suite
- Tested SAML with G Suite
- Tested LDAP
- Tested insecure mode (boo)
- Tested using an X509 secure 3 node cluster, sending data across nodes
with RPG and PostHTTP/ListenHTTP, a Jolt transform.
- Verified that controller services and reporting tasks are starting and
stopp
+1 (binding)
Running with openjdk version "11.0.16" 2022-07-19 LTS:
I tested this RC with a 3 node cluster with an external Zookeeper, and a
test flow and found things to be working fine.
Also tested authentication with LDAP, SAML, OIDC and X509.
Thanks for the release work!
Nathan
On Fri, Sep
Hi,
I reverified the hashes and compiled from source with OpenJDK Runtime
Environment Zulu11.58+15-CA.
Ran a test cluster again and verified my cluster test flow still works as
expected.
+1 binding
Nathan
On Mon, Oct 3, 2022 at 4:45 PM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling
We might also want https://issues.apache.org/jira/browse/NIFI-10787
On Tue, Nov 15, 2022 at 4:05 PM Mark Bean wrote:
> I will be on it in about 2 hours, if not addressed sooner.
>
> On Tue, Nov 15, 2022 at 3:46 PM Joe Witt wrote:
>
> > NIFI-10703 would be great to get in. Just a matter of gett
I'll take a look at the PR you submitted for it
On Fri, Dec 2, 2022 at 4:50 PM Mark Payne wrote:
> -1 (binding)
>
> In doing some testing, I encountered a couple of bugs. Most were minor,
> but I would consider NIFI-10937 [1] critical enough to sink the release.
> It results in a failure to star
+1 binding
Verified functionality on 3 node NiFi cluster and test flows
Verified X509 login for NIFi
Verified OIDC login/logout in NiFi and NiFi Registry
Verified LDAP login/logout for NiFi and NiFi Registry
On Tue, Dec 6, 2022 at 5:56 PM Nandor Soma Abonyi
wrote:
> +1 (non-binding)
>
> - Went
+1 (binding)
The proposal sounds great to me
On Wed, Dec 14, 2022, 1:01 PM Edward Armes wrote:
> -1 (non-binding)
>
> Im not sure if this is covered by 8 and 5 , but I would like to suggest
> that as part of 2.0 focus on removing places were concrete implementations
> are used over interfaces
Hi Edison,
It sounds like your nifi-registry.properties file may have issues. Can you
share this section of configuration nifi.registry.web.https.host=?
nifi.registry.web.https.port=?
This guide should be able to help:
https://community.cloudera.com/t5/Community-Articles/Setting-Up-a-Secure-Apach
egistry.web.http.host=
> nifi.registry.web.http.port=
> nifi.registry.web.https.host=127.0.0.1
> nifi.registry.web.https.port=19443
>
>
> Best Regards,
> ------
> *From: *"Nathan Gough"
> *To: *"dev"
> *Cc: *"ED
/
> NiFi Registry home: /home/edinaranjoespin/NiFi/nifi-registry-1.19.0
>
> Bootstrap Config File:
> /home/edinaranjoespin/NiFi/nifi-registry-1.19.0/conf/bootstrap.conf
>
> 2023-01-12 11:07:24,044 INFO [main]
> o.apache.nifi.registry.bootstrap.Command Apache NiFi Registry is no
. Will
> not restart NiFi Registry
> 2023-01-16 12:22:06,990 INFO [main]
> o.apache.nifi.registry.bootstrap.Command Apache NiFi Registry is not running
>
> ==> nifi-registry-event.log <==
>
>
> At the moment, nifi-registry its running over http only. With https
> pe
Hi Riyaz,
Images don't come through on the mail list so you will need to post a link
to the image or copy and paste the log here.
Thanks,
Nathan
On Fri, Nov 29, 2024, 11:15 AM Riyaz Mohammed wrote:
> Hi,
>
> I am using Nifi 2.0 and starting it using nifi.cmd start command
> But in actually doe
53 matches
Mail list logo
