Member since
12-22-2020
3
Posts
0
Kudos Received
0
Solutions
12-29-2020
02:37 AM
@MattWho We tried two different bucket settings: one publicly visible, the other not We are logged into NiFi and to NiFi Registry with the NiFi Admin user. Could this cause a problem? The NiFI Controller Settings look like this:
... View more
12-28-2020
07:23 AM
Thank you @MattWho Our whole setup is very basic so far. We are working with the admin user and authenticate with the generated client certificates (nifi toolkit). We have no additional user authorization in place yet. Therefore also no identity mapping patterns. Also used the exact domain name as user CN. When trying to perform version control, the nifi registry log gives the requested resource followed by a repetition of these messages: IdentityFilter Attempting to extract user credentials using X509IdentityProvider IdentityFilter Adding credentials claim to SecurityContext to be authenticated. Credentials extracted by X509IdentityProvider: AuthenticationRequest{username='CN=nifi_admin, OU=NiFi', credentials=[PROTECTED], details=org.apache.nifi.registry.web.security.authentication.x509.X509AuthenticationRequestDetails@3938d0ef} IdentityFilter Credentials already extracted for [org.apache.nifi.registry.web.security.authentication.AuthenticationRequestToken$1@138d2a4], skipping credentials extraction filter using JwtIdentityProvider AnonymousIdentityFilter SecurityContextHolder not populated with anonymous token, as it already contained: 'AuthenticationRequest{username='CN=nifi_admin, OU=NiFi', credentials=[PROTECTED], details=org.apache.nifi.registry.web.security.authentication.x509.X509AuthenticationRequestDetails@1a175871}' ResourceAuthorizationFilter Request filter authorization check is not required for this HTTP Method on this resource. Allowing request to proceed. An additional authorization check might be performed downstream of this filter. ProxyChainAuthorizable Requested resource is /tenants This is the only remarkable message but I don't see any obvious error.
... View more
12-22-2020
05:26 AM
Hello all, Here is our setup: -set up secure nifi -set up secure registry -both on the same machine -created user in registry with CN=[hostname], OU=NiFi with read right on buckets and proxy user requests enabled -created Registry client in the nifi instance with https://[hostname]:[port] -when trying to start version control on a process group, buckets are loading for a split second, then showing -> "no available buckets" -activated logging on DEBUG level, can see the proxy request, but no authorization -when listening to the registry port with netstat, we can see registry listening on that port -when trying to retrieve buckets through nifi, connection is established, but no buckets can be seen Additional information: We have created buckets, adding both the admin user and the user which is used for the connection in registry to their policies. We encounter no error when trying to retrieve the buckets, neither in the UI nor anywhere in the logs (with highest logging level activated). We have seen several set up videos and many open threads but the suggested solutions are not solving our problem. We suspect a permission problem, but are unable to detect the root of the problem if necessary logs can be provided.
... View more
Labels:
- Labels:
-
NiFi Registry