Re: [EXTERNAL] Re: Re: writing to adls - NiFi on Azure

networks and IP addresses” > > > > Where can I see the full stack trace? > > > > Thanks > > > > *From:* Peter Turcsanyi > *Sent:* Thursday, June 6, 2024 1:39 AM > *To:* users@nifi.apache.org > *Subject:* [EXTERNAL] Re: Re: writing to adls - NiFi on Azure &

RE: [EXTERNAL] Re: Re: writing to adls - NiFi on Azure

Hi Peter, It is “Enabled from selected virtual networks and IP addresses” Where can I see the full stack trace? Thanks From: Peter Turcsanyi Sent: Thursday, June 6, 2024 1:39 AM To: users@nifi.apache.org Subject: [EXTERNAL] Re: Re: writing to adls - NiFi on Azure ATTENTION: This email

RE: Who or what sets up NIFI_HOME as a system environment variable?

Hi Russell, To set that variable up as a system environment variable requires the installer to do something, like add the export command to a file such as “/etc/environment”. That is what we do on our current project, and I can see it happening in an Ansible task. An out of the box

RE: Processor Python Creation

Hi Luis, I've observed similar behavior working with the python processors. > 1. Everytime I modify the python code of a processor and stop it, all > the dependencies are re-installed. Doesn't matter if I just changed code > or added any new library. Is that ok ? The modification

Re: [EXTERNAL] Re: writing to adls - NiFi on Azure

; > > Thanks > > > > *From:* Peter Turcsanyi > *Sent:* Friday, May 31, 2024 4:17 PM > *To:* users@nifi.apache.org > *Subject:* [EXTERNAL] Re: writing to adls - NiFi on Azure > > > > *ATTENTION:* This email originated from outside of GM. > > > > > H

Re: Nifi 2.0-M3 cannot set attributes

Thank you for the quick answer David. I guess the only option for now is to wait... Regards, LC El 05-06-24 a las 17:29, David Handermann escribió: Hi Luis, Thanks for reporting this problem and providing the background details. This is a known issue related to applying FlowFile

Re: Nifi 2.0-M3 cannot set attributes

Hi Luis, Thanks for reporting this problem and providing the background details. This is a known issue related to applying FlowFile attributes with the failure relationship, and it is being tracked in the follow Jira issue: https://issues.apache.org/jira/browse/NIFI-13324 Regards, David

Re: PutUDP using flowfile attribute in nifi 1.22.0

This is obviously help us in moving forward to our next step. Since we have to load-balance udp packets to multiple Nifi servers for that we use F5 BigIP load balancer. This adds one more problem to solve for us. However, we have solved that problem in our custom Java application which listens

Re: PutUDP using flowfile attribute in nifi 1.22.0

Hi Atul, To clarify, would your user case work if Hostname and Port properties were enhanced to support evaluating expression language using the flow files? Regards, Jim > On Jun 4, 2024, at 8:41 AM, Atul Saroha wrote: > > Hi All, > > We recently started using nifi for the last 6 months. We

RE: [EXTERNAL] Re: writing to adls - NiFi on Azure

Hi Peter, We tried that , still does not work. Same error. Thanks From: Peter Turcsanyi Sent: Friday, May 31, 2024 4:17 PM To: users@nifi.apache.org Subject: [EXTERNAL] Re: writing to adls - NiFi on Azure ATTENTION: This email originated from outside of GM. Hi Tahir, I tested it without

Re: Back pressure in a NiFi cluster

Thanks for the confirmation! Am Di., 4. Juni 2024 um 14:57 Uhr schrieb Pierre Villard < pierre.villard...@gmail.com>: > Hi Alexis, > > Backpressure is a node-level concept. If there is backpressure on one > node, it does not impact other nodes. So the statement "it could be that 1 > node is

RE: Back pressure in a NiFi cluster

Alexis, I see this often in some of the clusters I maintain. The restricted scheduling only applies to the node where the back pressure is occurring. The red and amber colours on the UI are there as a clue to the user that back pressure is occurring. You can test this for example by using the

Re: Back pressure in a NiFi cluster

Hi Alexis, Backpressure is a node-level concept. If there is backpressure on one node, it does not impact other nodes. So the statement "it could be that 1 node is slower and reaches the threshold while the others run normally" is correct. HTH, Pierre Le mar. 4 juin 2024 à 14:54, Alexis

Re: Single Batch Per Node and back pressure

Got it, thanks for the clarification. On Mon, 3 Jun 2024, 18:00 Michael Moser, wrote: > When ControlRate yields, it will yield for the full Yield Duration. So > your scenario, Alexis, will allow 10 files through in the first > half-second, and when the 11th arrives it will yield for 1 second

Re: Single Batch Per Node and back pressure

When ControlRate yields, it will yield for the full Yield Duration. So your scenario, Alexis, will allow 10 files through in the first half-second, and when the 11th arrives it will yield for 1 second (if Yield Duration = 1 sec). After that yield ends, it will allow the next 10 files through

Re: Single Batch Per Node and back pressure

Hi Jim, Thanks for the prompt response. I think that could work, but now that I look at it, the documentation says that accuracy can be increased "by decreasing the Yield Duration" - if I want, say, 10 files per second and 20 arrive evenly spread out within a second, does that mean that after

Re: Single Batch Per Node and back pressure

Hi Alexis, Yes, what you see in your experiments is the expected behavior. The NiFi documentation for FlowFileCurrency says: SINGLE_BATCH_PER_NODE When

RE: [JDK] NiFi 1.20.0 comaptibility with JDK21

do el: lunes, 3 de junio de 2024 14:00 Para: users@nifi.apache.org Asunto: Re: [JDK] NiFi 1.20.0 comaptibility with JDK21 NTT DATA Security Awareness - This is an incoming mail from an EXTERNAL SENDER (users-return-17480-pedro.soto.fernandez=nttdata@nifi.apache.org<mailto:use

Re: [JDK] NiFi 1.20.0 comaptibility with JDK21

Hi Pedro, It's hard to have a definitive answer on this as it also depends on what you're using in your flows but you may have some issues. I'd highly recommend using the latest of Apache NiFi 1.x (NiFi 1.26) if you want to run it with Java 21. Thanks, Pierre Le lun. 3 juin 2024 à 13:56, Pedro

RE: Single Batch Per Node and back pressure

My reading of the manual on this suggests that the batch size is determined by the contents of the queue upstream of the input node, not the downstream queue. "... the Input Ports will continue to ingest all data until all of the queues feeding the Input Ports have been emptied." Perhaps

Re: writing to adls - NiFi on Azure

Hi Tahir, I tested it without permissions and got a different error message: "code":"AuthorizationPermissionMismatch","message":"This request is not authorized to perform this operation using this permission. So the role/permissions should not be an issue in your environment. For your error

Re: writing to adls - NiFi on Azure

R, You can unsubscribe by sending an email to users-unsubscr...@nifi.apache.org . Best, Peter Turcsanyi On Fri, May 31, 2024 at 10:11 PM R wrote: > please remove me from this list > > On Fri, May 31, 2024 at 4:04 PM Peter Turcsanyi > wrote: > >> Hi Tahir, >> >> Did you configure

RE: [EXTERNAL] Re: writing to adls - NiFi on Azure

Yes, we configured managed identity for our VM. We provided Storage blob contributor role, also tried using Blob data owner. Thanks From: Peter Turcsanyi Sent: Friday, May 31, 2024 3:04 PM To: users@nifi.apache.org Subject: [EXTERNAL] Re: writing to adls - NiFi on Azure ATTENTION: This email

Re: writing to adls - NiFi on Azure

please remove me from this list On Fri, May 31, 2024 at 4:04 PM Peter Turcsanyi wrote: > Hi Tahir, > > Did you configure system-assigned or user-assigned managed identity for > your VM on the Azure portal? > Did you grant the right role (e.g. Storage Blob Data Owner) to that > managed identity?

Re: writing to adls - NiFi on Azure

Hi Tahir, Did you configure system-assigned or user-assigned managed identity for your VM on the Azure portal? Did you grant the right role (e.g. Storage Blob Data Owner) to that managed identity? Best regards, Peter Turcsanyi On Fri, May 31, 2024 at 8:10 PM Tahir Khan wrote: > Hi, > > We are

RE: Authorisation with multi-tiered groups

Hi all, I didn't get much traction when I raised this question a few weeks ago. Is there any appetite for re-addressing the Jira ticket mentioned? Regards Steve Hindmarch From: stephen.hindmarch.bt.com via users Sent: Friday, April 12, 2024 12:15 PM To: users@nifi.apache.org Subject

RE: [SSL] Can't reach remote site, SSL error

just gone. Thanks Emmanuel De : Isha Lamboo Envoyé : lundi 6 mai 2024 08:51 À : users@nifi.apache.org Objet : RE: [SSL] Can't reach remote site, SSL error CAUTION: This message originated from an outside organization. In case of suspicion, click on "Report to SAFRAN Security" from t

RE: Re: Re: Re: IMDSv2 + Hashicorp Vault

ted] From: David Handermann Sent: Wednesday, May 8, 2024 17:00 To: users@nifi.apache.org Subject: [EXTERNAL] Re: Re: Re: IMDSv2 + Hashicorp Vault Brant, Thanks for the additional details. Based on the description, it sounds like it would be worth raising an issue with Spring Vault. The NiFi impl

Re: Re: Re: IMDSv2 + Hashicorp Vault

dermann > *Sent:* Wednesday, May 8, 2024 14:38 > *To:* users@nifi.apache.org > *Subject:* [EXTERNAL] Re: Re: IMDSv2 + Hashicorp Vault > > > > Brant, Just for clarification, Spring Vault is a separate project from > Spring Framework, following its own version numbering strateg

RE: Re: Re: IMDSv2 + Hashicorp Vault

mann Sent: Wednesday, May 8, 2024 14:38 To: users@nifi.apache.org Subject: [EXTERNAL] Re: Re: IMDSv2 + Hashicorp Vault Brant, Just for clarification, Spring Vault is a separate project from Spring Framework, following its own version numbering strategy, so Spring Vault 3. 1.  1 is the latest versi

Re: Re: IMDSv2 + Hashicorp Vault

k background with green text Description automatically > generated] > > > > *From:* Patrick Timmins > *Sent:* Wednesday, May 8, 2024 11:45 > *To:* users@nifi.apache.org > *Subject:* [EXTERNAL] Re: IMDSv2 + Hashicorp Vault > > > > In my best Rosanne Rosanadana .. . never

RE: Re: IMDSv2 + Hashicorp Vault

2024 11:45 To: users@nifi.apache.org Subject: [EXTERNAL] Re: IMDSv2 + Hashicorp Vault In my best Rosanne Rosanadana .. . never mind .. . I see the only outlier for using the latest Spring is the spring-vault-core-3. 1. 0. jar !! On 5/8/2024 11: 20 AM, Brant Gardner wrote: We’re running 2. 0. 0

Re: IMDSv2 + Hashicorp Vault

gard...@solventum.com* *A black background with green text Description automatically generated *From:*Patrick Timmins *Sent:* Wednesday, May 8, 2024 11:00 *To:* users@nifi.apache.org *Subject:* [EXTERNAL] Re: IMDSv2 + Hashicorp Vault What version of NiFi are you using? I'm seeing Spring v5. 3. 30 in Ni

Re: IMDSv2 + Hashicorp Vault

From:*Patrick Timmins *Sent:* Wednesday, May 8, 2024 11:00 *To:* users@nifi.apache.org *Subject:* [EXTERNAL] Re: IMDSv2 + Hashicorp Vault What version of NiFi are you using? I'm seeing Spring v5. 3. 30 in NiFi 1. 24. On 5/8/2024 6: 32 AM, Brant Gardner wrote: Good morning, It appears that the Spring

RE: Re: IMDSv2 + Hashicorp Vault

To: users@nifi.apache.org Subject: [EXTERNAL] Re: IMDSv2 + Hashicorp Vault What version of NiFi are you using? I'm seeing Spring v5. 3. 30 in NiFi 1. 24. On 5/8/2024 6: 32 AM, Brant Gardner wrote: Good morning, It appears that the Spring 3. 1. 0 libraries that NiFi uses are unable to work with IMDSv2 o

Re: IMDSv2 + Hashicorp Vault

What version of NiFi are you using?  I'm seeing Spring v5.3.30 in NiFi 1.24. On 5/8/2024 6:32 AM, Brant Gardner wrote: Good morning, It appears that the Spring 3.1.0 libraries that NiFi uses are unable to work with IMDSv2 on AWS EC2 instances, so if your company requires IMDSv2 (which ours

RE: [SSL] Can't reach remote site, SSL error

or proprietary information and may be subject to export control laws and regulations. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. Unauthorize

RE: Restarting Nifi Cluster Systems to add new user

as Joe has pointed out. Regards, Isha Van: Joe Witt Verzonden: woensdag 1 mei 2024 00:42 Aan: users@nifi.apache.org Onderwerp: Re: Restarting Nifi Cluster Systems to add new user Thanks - take a look at your conf/authorizers file and see which authorizer is being used. Based on what you said

Re: Restarting Nifi Cluster Systems to add new user

Thanks - take a look at your conf/authorizers file and see which authorizer is being used. Based on what you said it sounds like org.apache.nifi.ldap.tenants.LdapUserGroupProvider There are properties related to how aggressively it will search for information from the directory server. The

Re: Restarting Nifi Cluster Systems to add new user

Hello Joe, It's through AD. But it isn't controlled via groups. I ended up having to add the user through the UI (which will normally be overwritten). I'm running version 1.23.2. Regards, *Shamsudeen Jameer*Data Operations managerpriorityshamsudeen.jam...@prth.como: (516) 345-5015 M: (917)

Re: Restarting Nifi Cluster Systems to add new user

Hello Can you share more about which authentication and authorization provider you're using with NiFi today? Also would be good to share which other authentication/authorization providers your organization could leverage as then it is a question of which ones are supported out of the box.

Re: Insufficient permissions on initial start up (NiFi 2.0)

No problem. Glad you got it sorted. Yet at the https URL in the browser, it still tells me it is insecure. > This is happening because the certificate is not issued by a trusted Certificate Authority. The certificate from TinyCert is valid (the connection works) but TinyCert is not a trusted CA

Re: Python Processor and relationships

Hi, Are you in a position to share the code of your python processor? Did you implement getRelationships(self) in your processor? Le ven. 26 avr. 2024, 06:52, Ashwini Kumar a écrit : > I created a Python Nifi Processor just as in the standard python > documentation. This is NOT an

Re: Insufficient permissions on initial start up (NiFi 2.0)

When I learned that the initial user in authorizers.xml must match the certificate *exactly*, I figured it would be an easy matter to use openssl to inspect the cert. I wanted to be *absolutely* certain I matched it correctly. Here is the command: /opt/nifi/config_resources/keys$ openssl pkcs12

Re: Insufficient permissions on initial start up (NiFi 2.0)

> > What is this Access Token it cites at top? > NiFi UI attempts to get the access token expiration. However, since you're authenticating with a certificate the endpoint returns an IllegalState because there was no token in the request. Looking at the logs and the supplied configuration it

Re: Insufficient permissions on initial start up (NiFi 2.0)

The identity you put for your initial admin is: C = US, ST = Virginia, L = Reston, O = C4 Rampart, OU = NIFI, CN = admin2 Which does not match the identity shown in the logs that is coming from your client cert: CN=admin2, OU=NIFI, O=C4 Rampart, L=Reston, ST=Virginia, C=US It is case and

Re: Insufficient permissions on initial start up (NiFi 2.0)

Looking at the nifi-user.log, I find I am getting a Conflict response, Access Token not found. more ./nifi-user.log 2024-04-25 00:23:49,329 INFO [main] o.a.n.a.FileUserGroupProvider Creating new users file at /opt/nifi/config_resources/users.xml 2024-04-25 00:23:49,352 INFO [main]

Re: Insufficient permissions on initial start up (NiFi 2.0)

James, If you check the nifi-user.log in the logs directory, you should see messages for the requests that are being rejected. In that log message you should see the identity that you're authenticated with. Can you compare that with the user that you've configured the policies for. Hopefully,

Re: Insufficient permissions on initial start up (NiFi 2.0)

I still cannot access my own NiFi 2.0 instance. I continue to get this rejection: Insufficient Permissions - home Unable to view the user interface. Contact the system administrator. The canvas flashes for an instant when I try to hit my secure URL, but is immediately replaced with this

Re: Insufficient permissions on initial start up (NiFi 2.0)

I'll review this closely once again when I get back to this system tonight - thanks very much for your reply, Isha. I also feel I need to look more closely in nifi.properties, at values I have set for keys nifi.security.identity.mapping.[value, transform, pattern].CN1 I noticed some odd behavior

RE: Insufficient permissions on initial start up (NiFi 2.0)

Hi James, Have you changed these settings in authorizers.xml since you first started NiFi? If so, you may need to delete users.xml and authorizations.xml. A new admin user will not be created if those files already exist. Otherwise, the trickiest part is usually that the user DN needs to match

Re: How to upload flow definition to new 2.0 instance?

Thank you Pierre. I appreciate your reply. I have not yet done this but intend to, as soon as I can figure out how to get my NiFi 2.0 instance to come up securely with certs and TLS. I do and did not want to load up my flows into a nonsecured NiFi instance, which is why I have taken so long to

Re: Unable to securely connect to NiFi 2.0 instance

> Regards, > > > > Isha > > > > > > *Van:* James McMahon > *Verzonden:* vrijdag 19 april 2024 01:17 > *Aan:* users > *Onderwerp:* Re: Unable to securely connect to NiFi 2.0 instance > > > > I started from scratch. Got nifi to start, no errors at

RE: Unable to securely connect to NiFi 2.0 instance

which CAs it will accept for client certs. Regards, Isha Van: James McMahon Verzonden: vrijdag 19 april 2024 01:17 Aan: users Onderwerp: Re: Unable to securely connect to NiFi 2.0 instance I started from scratch. Got nifi to start, no errors at all in my nifi-app.log. Configured the client

Re: Unable to securely connect to NiFi 2.0 instance

I started from scratch. Got nifi to start, no errors at all in my nifi-app.log. Configured the client certs in my Chrome browser, also added cacert.pem to my Root Trusted CAs. Tried to hit https://ec2-44-219-227-80.compute-1.amazonaws.com:8443/nifi , continue to get rejected with this message from

Re: How to upload flow definition to new 2.0 instance?

In NiFi 1.x, right click on process group, download flow definition. It'll give you a JSON file. In NiFi 2, drag and drop a process group on the canvas, and click the upload icon on the right of the name input. You'll be able to select your JSON file. HTH Le jeu. 11 avr. 2024 à 02:14, James

Re: Hit\Miss Writing to Syslog system

Hi Shamsudeen, Thanks for the reply and clarifying the use of the protocol. UDP does not offer any kind of delivery guarantees at the protocol level, so it is even less reliable than TCP for syslog. In other words, data loss can happen without any type of error being logged. If the data loss is

Re: Hit\Miss Writing to Syslog system

Hi David, Thanks for the information. I'm actually using the UDP port to transfer logs to the syslog system. Planning to upgrade to TCP in the future but just need to figure out why it's hit \ miss. Regards, *Shamsudeen Jameer* On Thu, Mar 28, 2024 at 10:37 PM David Handermann <

Re: Hit\Miss Writing to Syslog system

Hi Shamsudeen, Although TCP incorporates packet acknowledgement as a core feature of the protocol, syslog does not provide any type of delivery guarantees on top of TCP. This means that it is possible for a system such as NiFi to send a syslog message, without logging a socket communication

Re: java.lang.OutOfMemoryError: Java heap space : NIFI 1.23.2

. > > Regards > > > *Envoyé:* mardi 19 mars 2024 à 14:53 > *De:* "Joe Witt" > *À:* users@nifi.apache.org > *Objet:* Re: java.lang.OutOfMemoryError: Java heap space : NIFI 1.23.2 > Hello > > The key output is > > java.lang.OutOfMemoryError: Jav

Re: java.lang.OutOfMemoryError: Java heap space : NIFI 1.23.2

; to 1 and it is worked.   Regards     Envoyé: mardi 19 mars 2024 à 14:53 De: "Joe Witt" À: users@nifi.apache.org Objet: Re: java.lang.OutOfMemoryError: Java heap space : NIFI 1.23.2 Hello   The key output is   java.lang.OutOfMemoryError: Java heap space Review batch prope

Re: java.lang.OutOfMemoryError: Java heap space : NIFI 1.23.2

Specifically set Fetch Size to something like 1000, by default setting Fetch Size to zero will cause Postgres to fetch the entire ResultSet into memory [1]. We should probably change that default to avoid problems like this and with other drivers (for example, Oracle's default is 10 rows which is

Re: java.lang.OutOfMemoryError: Java heap space : NIFI 1.23.2

Hello The key output is java.lang.OutOfMemoryError: Java heap space Review batch property options to limit response sizes in the database calls. Thanks On Tue, Mar 19, 2024 at 6:15 AM wrote: > Hello > > I got the executeSQL processor does the sql command "select * from > public.table1" >

Re: Error on first launch (probable newbie misconfiguration)

Hi Mark, thanks for your feedback. In nifi-app.log, the last stacktrace seems pretty explicit: Caused by: org.apache.nifi.encrypt.EncryptionException: Key Password length less than required [12] at

Re: Error on first launch (probable newbie misconfiguration)

Franck, Can you take a look at the nifi-app.log? That should provide more information than the bootstrap log does. Thanks -Mark > On Mar 14, 2024, at 5:09 AM, Franck Routier via users > wrote: > > Any idea anyone ? > > Le jeudi 7 mars 2024, 09:08:45 CET Franck Routier a écrit : >> Hi, >>

Re: Error on first launch (probable newbie misconfiguration)

Any idea anyone ? Le jeudi 7 mars 2024, 09:08:45 CET Franck Routier a écrit : > Hi, > > here is the result of the launch: > > root@nifi:/opt/nifi# bin/nifi.sh run > nifi.sh: JAVA_HOME not set; results may vary > > Java home: > NiFi home: /opt/nifi-2.0.0-M2 > > Bootstrap Config File:

Re: MergeRecord takes too much time

I’m not an expert with MergeRecord, but looking at your screenshots, I’d guess that your setup is taking that long to reach one of the defined “maximum” settings, e.g. 2GB, 5,000,000 records, or 3600 seconds (1 hour). How large (number of records and content size in bytes) are the typical

Re: Why are my journal files so large on node 2 of cluster?

David, Makes sense. Large values should not be added as attributes. Attributes are designed for String values. Think 100-200 characters, generally. A couple KB can be fine, as well, but it can significantly reduce performance. If the intent is to “stash the content” so that you can change it

Re: Why are my journal files so large on node 2 of cluster?

Mark, Yes, it was the flowfile repository. Of all your points, the large attributes is most likely our issue. One of our folks was caching the flowfile (which can be large occasionally) in an attribute ahead of a DB lookup (which would overwrite the contents) and then reinstating the content

Re: Integrate NiFi auth using OKTA SAML

Thanks David. I will try then share it again. :) Regards, DongCheol Gong 2024년 3월 5일 (화) 오후 10:38, David Handermann 님이 작성: > Thanks for following up on this issue, the additional logging is helpful. > > The example URL provided does not include the port number ( > https://nifi.my-site.com)

Re: SELinux and NiFi

Similar situation here. Not a devops guy. So I guess it’s fair to say this is expected behavior if policies are not written to allow nifi.sh and such to access the folders NiFi needs to access. Thanks for the help.Sent from my iPhoneOn Mar 8, 2024, at 5:38 PM, Russell Bateman wrote:

Re: SELinux and NiFi

That's what lies in those "SELinux policies." I think it's simple: Use SELinux to lock the filesystem (and other stuff) up so no one can get in or go around. Then create specific policies that allow, in this case, NiFi, access to its filesystem (like //opt/nifi/current-nifi//) so that it can

Re: SELinux and NiFi

I think the admin told me that even a simple nifi.sh start won’t work. Just won’t even start the script and it is marked executable. I was wondering if there were any gotchas to getting a basic setup running. Sent from my iPhone > On Mar 8, 2024, at 4:29 PM, Russell Bateman wrote: > >  We

Re: SELinux and NiFi

We have run on CentOS with SELinux set to enforcing and have run NiFi in that environment for probably 8 or 9 years now. We do install some SELinux policies that allow NiFi to access the filesystem underneath itself and not outside that filesystem. What specifically are you asking? On 3/8/24

Re: Why are my journal files so large on node 2 of cluster?

Dave, When you say that the journal files are huge, I presume you mean the FlowFile repository? There are generally 4 things that can cause this: - OutOfMemoryError causing the FlowFile repo not to properly checkpoint - Out of Disk Space causing the FlowFile repo not to properly checkpoint -

Re: RestLookupService question

ticket for the improvement. Look for the > > *Dynamic Properties:* > Supports Sensitive Dynamic Properties: *Yes* > > in the processor usage. > Lehel > -- > *From:* Roman Wesołowski > *Sent:* Thursday, March 7, 2024 17:48 > *To:* users@nifi.apache.org

Re: RestLookupService question

Sent: Thursday, March 7, 2024 17:48 To: users@nifi.apache.org Subject: Re: RestLookupService question Hi, I have an additional question regarding RestLookupService. I will use this thread. When we add a header in InvokeHTTP processor we can set "Sensitive Value" Yes/No, however dur

Re: RestLookupService question

; *From:* Gregory Foreman > *Sent:* Thursday, March 7, 2024 12:53 > *To:* users@nifi.apache.org > *Subject:* Re: RestLookupService question > > I assume this is a bug. I just created NIFI-12875 ( > https://issues.apache.org/jira/browse/NIFI-12875) to track. > > On M

Re: RestLookupService question

The response code is only used in debug logs, there is room to improve error handling, Thanks for reporting! From: Gregory Foreman Sent: Thursday, March 7, 2024 12:53 To: users@nifi.apache.org Subject: Re: RestLookupService question I assume this is a bug. I

Re: RestLookupService question

I assume this is a bug. I just created NIFI-12875 (https://issues.apache.org/jira/browse/NIFI-12875) to track. > On Mar 1, 2024, at 8:04 AM, Gregory Foreman > wrote: > > Hello: > > The RestLookupService service seems to treat all http response status codes > the same. Is this intentional?

Re: Error on first launch (probable newbie misconfiguration)

Hi, here is the result of the launch: root@nifi:/opt/nifi# bin/nifi.sh run nifi.sh: JAVA_HOME not set; results may vary Java home: NiFi home: /opt/nifi-2.0.0-M2 Bootstrap Config File: /opt/nifi-2.0.0-M2/conf/bootstrap.conf 2024-03-07 08:05:28,742 INFO [main]

Re: Error on first launch (probable newbie misconfiguration)

Hey there Franck, Can you provide the full error message with stack trace that gets printed? Thanks -Mark On Mar 6, 2024, at 1:26 PM, Franck Routier via users wrote: Hi, I'm a first time wanabe user of Nifi, and I followed the installation guide, until the point when I try to launch Nifi:

Re: Integrate NiFi auth using OKTA SAML

Thanks for following up on this issue, the additional logging is helpful. The example URL provided does not include the port number ( https://nifi.my-site.com) which seems to imply the presence of a gateway or reverse proxy server in front of NiFi. This configuration is supported, but in some

Re: Integrate NiFi auth using OKTA SAML

Hi guys. I solved and share my story. I was able to check the logs that the destination information was different as shown below, but there was no problem with the settings in OKTA. 2024-03-04 12:14:33,051 DEBUG [NiFi Web Server-26] o.s.s.s.p.s.a.OpenSamlAuthenticationProvider Found 2

Re: Integrate NiFi auth using OKTA SAML

Thanks David, I know it's not going to be easy to resolve my issue. I'll change the loglevel as you suggested and test again. Have a nice and happy weekend. Regard, DongCheol Gong 2024년 3월 1일 (금) 오전 10:36, David Handermann 님이 작성: > Thanks for providing some background on the issue with SAML

Re: Integrate NiFi auth using OKTA SAML

Thanks for providing some background on the issue with SAML configuration. The following post describes the steps required for configuring NiFi to integrate with Okta, including example configuration settings:

Re: Insufficient Permissions - Unable to view the user interface - at WebUI

rn...@domain.com as "Initial User Identity 1" and "Initial Admin > Identity" in authorizers.xml? > > > > 2.2) If one is using DN "Initial User Identity 1" and "Initial Admin > Identity" in authorizers.xml and the "USE_DN" for "

Re: Smb processor landscape

Hi Anders, you are not alone :-) I've the same issue and have tried to create some other jira's for a long time ago. FetchSmb: Addind completing strategy - https://issues.apache.org/jira/browse/NIFI-12231?filter=-2 PutSmb: Add a rename strategy

Re: InvokeHttp - Provenance Events

Mark: Ok, thanks for clarifying. Greg > On Feb 26, 2024, at 11:38 AM, Mark Payne wrote: > > Greg, > > Yes, the Relationship is generally only populated for ROUTE events, such as > RouteOnAttribute. > > Thanks > -Mark > > >> On Feb 26, 2024, at 11:34 AM, Gregory Foreman >> wrote: >> >>

Re: InvokeHttp - Provenance Events

Greg, Yes, the Relationship is generally only populated for ROUTE events, such as RouteOnAttribute. Thanks -Mark > On Feb 26, 2024, at 11:34 AM, Gregory Foreman > wrote: > > Hello: > > I am having an issue with the InvokeHttp processor provenance events. No > Relationship field is

RE: Insufficient Permissions - Unable to view the user interface - at WebUI

hat should one use as "User Search Filter" in login-identity-providers.xml? Thanks From: Matthew Clarke Sent: Sunday, February 25, 2024 11:19 PM To: users@nifi.apache.org Cc: Alexei Rozenvaser Subject: Re: Insufficient Permissions - Unable to view the user interface

Re: Insufficient Permissions - Unable to view the user interface - at WebUI

Hello Alexei, Since you are loving in using your sAMAccountName, I recommend using them identity string instead of the full DN of your AD users. In your ldap-provider, change USE_DN to USE_USERNAME. Upon successfully authentication the username you provided in the login window will be posted to

RE: Insufficient Permissions - Unable to view the user interface - at WebUI

t;Authentication Strategy" for LDAP-provider at my login-identity-providers.xml don't FileUserGroupProvider + FileAccessPolicyProvider enough at my authorizers.xml? From: Michael Moser Sent: Thursday, February 22, 2024 4:24 PM To: users@nifi.apache.org; Alexei Rozenvaser Subject: Re: Insufficie

RE: Insufficient Permissions - Unable to view the user interface - at WebUI

ary 22, 2024 4:33 PM To: users@nifi.apache.org Subject: Re: Insufficient Permissions - Unable to view the user interface - at WebUI You don't often get email from j...@thefribergs.com<mailto:j...@thefribergs.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification&

RE: Using PutIceberg to insert into a table in S3 fails with ClassNotFoundException

Hey Pierre, This has solved the issue for me. Thank you! From: Pierre Villard Sent: 23 February 2024 13:59 To: users@nifi.apache.org Subject: Re: Using PutIceberg to insert into a table in S3 fails with ClassNotFoundException I believe that you'd need to build the processor with specific

Re: Using PutIceberg to insert into a table in S3 fails with ClassNotFoundException

I believe that you'd need to build the processor with specific profiles enabled which is not the case in the default build that we provide for convenience. In nifi-inceberg-bundle, you could do something like maven clean install -Pinclude-hadoop-aws And use the generated NARs in your NiFi

Re: Track dataflow with counter / updatecounter / statefull

consider to done.   Also, I have tested the Notify and Wait, but I remember it is not working in the cluster environment.   Anyway, I'm trying to deal with these informations.   Thanks   Minh     Envoyé: mercredi 21 février 2024 à 16:49 De: "Lehel Boér" À: "users@nifi.apache

Re: java.lang.IllegalStateException: Connection pool shut down for many AWS processors

Hi, Thanks for bringing this to our attention and for the investigation. I have identified a potential root cause and created a JIRA ticket for it. https://issues.apache.org/jira/browse/NIFI-12836 The observed behavior, as described by you and confirmed through my debugging, aligns with a

Re: Insufficient Permissions - Unable to view the user interface - at WebUI

Did you use a different user to setup ldap then your AD user your trying to login with now? On Thu, Feb 22, 2024 at 6:59 AM Alexei Rozenvaser wrote: > Hi Everyone > > > > I have a brand new installation of NiFi 2.0. > > I configured LDAP user authentication. > I have my AD DN defined as both

Re: Insufficient Permissions - Unable to view the user interface - at WebUI

Hello Alexei, If you have configured an org.apache.nifi.ldap.LdapProvider in your NiFi login-identity-providers.xml for *authentication* then you will also have to configure an org.apache.nifi.ldap.tenants.LdapUserGroupProvider in your NiFi authorizers.xml for *authorization*. Some instructions

  1   2   3   4   5   6   7   8   9   10   >