nested exception is
org.apache.nifi.authorization.exception.AuthorizerCreationException:
org.apache.nifi.authorization.exception.AuthorizerCreationException: Unable
to locate node CN=ohlvnfiap004dd.oh.dev.dat.aws.vz-connect.net, OU=NIFI to
seed policies.
This means CN=ohlvnfiap004dd.oh.dev.dat.aws
I deleted the authorizations.xml and user.xml files on all the nodes of the
cluster and restarted the nodes.
The Nifi nodes do not start up and I see the following errors int he logs
now:-
2018-09-20 08:20:09,003 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Failed to start web server: Error
We have no wild cards in the certificates created.Each node certificate has a
unique CN name same as that of the hostname.
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Thanks for the suggestions.
I tried exactly the same step and deleted authorizations.xml and user.xml
from all the cluster nodes and tried starting the nodes.I am encountering
the below error while starting the nodes now and the node does not start
now.
2018-09-20 08:20:09,003 ERROR [NiFi logging
I believe the reason why you get the error is because you added the Node
Identities in authorizers.xml after you started your NiFi cluster once.
In short, when NiFi is starting for the first time, it'll detect that
authorizations.xml and users.xml do not exist and the files will be
automatically g
Thanks for the reply.Please find below the authorizations.xml and user.xml;-
Authorizations.xml:-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
user.xml:-
-
-
Errors in the user logs:-
2018-09-19 05:25:14,267 INFO [NiFi Web Server-22]
o.a.n.w.a.c.IllegalStateExceptionMapper java
A few things to note:
Between NiFi 1.3.0 and NiFi 1.7.0, the authorizer structure changed, as the
user and group provider was separated from the policy provider. This means
there are two components (UserGroupProvider) and (AccessPolicyProvider) that
are defined independently and compose the Man
Hi,
are your hosts registered in LDAP properly? If you don't want them to come
from LDAP then they should come from the file-user-group-provider as
initial user identities in addition to your "Initial User Identity 1".
Peter
On Tue, Sep 18, 2018 at 11:54 AM nifi-san wrote:
> Hello,
>
> We are
Sounds like a permission issue. Can you share the content of
/opt/app/resources/nifi/authorizations.xml to be sure that /proxy
permissions have been correctly set on the node entities?
Thanks,
Pierre
Le mar. 18 sept. 2018 à 11:54, nifi-san a écrit :
> Hello,
>
> We are trying to integrate Nifi-
Hello,
We are trying to integrate Nifi-7.1 with SSL and LDAP.
We have two different Nifi installation,one which is a standalone node and
the other which is a three node cluster.
Nifi Standalone:-
We were able to successfully integrate the Standalone node with SSL and
login to the Nifi UI with th
10 matches
Mail list logo