Sorry I missed to send the way I solved that.
By the way, I found this error when I try to use cluster, LDAP and SSL.
All was about the identity mapping.
The identity in certificate was something like
CN=node.amexio.ch, OU=users, OU=nifi, DC=amexio, DC=ch
And in fact from the LDAP it was
Asmath,
Upsert in SQL Server (without NiFi) can be difficult, and even
error-prone if concurrency is needed [1]. I suspect that's why it
hasn't been attempted in PutDatabaseRecord (well, via the MSSQL
adapter(s)) as of yet. I haven't tried it without creating a procedure
so I'm not sure if the
That’s interesting. How did you go about fixing it?
From: Etienne Jouvin
Sent: March-11-21 3:57 PM
To: users@nifi.apache.org
Subject: [EXT]Re: Issue between NiFi and NiFi Registry using SSL/LDAP in
OpenShift
Hello.
Il vas something really similar.
Message saying that there is a certificat
Thanks for the reply. I have taken a look at nifi and nifi-registry’s
keystore.jks and truststore.jks and observed the following:
Both has CA certificate identical to each other.
Both has keystore certificate with 1 entry that has 2 chainlength. They were
both issued by the CA identified in the
Hello.
Il vas something really similar.
Message saying that there is a certificat problem.
But in fact it was about thé use identity that was sent from NiFi to
registry.
In thé certificate, the node OU contained spaces between each fields,
something like CN=XXX, OU=DOMAIN, OU=COM
But the CN in
Hi,
I am looking for some help on how to deal with upserts/updates on SQL
Server with NIFI.
I get a flow file where the records are updated. Primary key are already
defined on the table.
I don't want to try the logic of delete and insert, is there a way to
handle upsert automatically with this
Typically this means that one of the certificates involved cannot be
validated - the truststore for either the client or the server does not
contain an associated CA or intermediate certificate to validate the
certificate being presented to it. You should verify that all of the
relevant
Hello everyone,
My NiFi has issue communicating with NiFi Registry.
Both are set up to authenticate and authorize using the same LDAP search
string, and SSL is setup in such way that users can login securely to each UI.
Individually, they are both working as expected. However, NiFi can't seem
Santiago,
OK great, i’m glad you were able to get it working. So I think the issue is
that the script, when the getRelationships() method is called, should return a
Set but appears to return a Set - probably a
Set>.
But the Objects that are in that Set are not of type Relationship - they are
I was successfull in recreating my experimental setup and the issue. With
what you told me about disabled processors, I understand know that a
service restart would be unhindered by the misbehaving processor. The
restart was successful and the restart on my original experimental setup
was also
Hi Mark,
I am seeing this error in the user log when trying to access the PG:
-
2021-03-11 16:37:44,758 INFO [NiFi Web Server-17664]
org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous)
GET http://../nifi-api/flow/cluster/summary (source ip:
Santiago,
I do imagine that NIFI-8266 may be related. However, a couple of things to
note. Validation is performed asynchronously. Meaning it’s done in the
background and not when you try to enter the Process Group. So validation
problems should not prevent you from entering the PG. Also, when
Hi all,
[Nifi-1.10.0]
I added an InvokeScriptedProcessor to my Process Group. When I added the
groovy script as the body to the processor, the frontend kicked me out with
a generic error message and a link to nifi-home.
I can navigate to home and to other PGs but every time I try to get into my
13 matches
Mail list logo
