Thanks for support @MattWho . I overlooked that sticky session part but after configuring the sticky session on the load balancer everything is working fine. ... View more

Hello @MattWho    Load balancer started showing the login page after setting below properties in nifi.properties nifi.web.proxy.context.path=/ nifi.web.proxy.host=myapp.dev.domain.com:8443  (load balancer url)   but after giving the logins details nifi canvas is not coming up I am seeing the below error while access via load balancer URL in nifi-user.log file   2023-04-06 15:04:35,861 INFO [NiFi Web Server-17] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started 10.1xx.xx.xxx [<anonymous>] GET https://myapp.dev.domain.com:8443/nifi-api/flow/current-user 2023-04-06 15:04:35,862 WARN [NiFi Web Server-17] o.a.n.w.s.NiFiAuthenticationFilter Authentication Failed 10.1xx.xx.xxx GET https://myapp.dev.domain.com:8443/nifi-api/flow/current-user [Anonymous authentication has not been configured.]   I am using LDAP for authentication.   Do I need to change any other properties/settings, please help ... View more

I have configured this and set the  nifi.web.proxy.host: node1.domain.com:8443,node2.domain.com:8443,node3.domain.com:8443,loabalancerUrl.domain.com:8443 but while logging in I see below issue. I have checked the logs but no errors in nifi-user.logs   ... View more

Thanks for the reply @MattWho I have implemented in the same way what you have said but while accessing with the load balancer url I am getting the below exception   System Error The request contained an invalid host header [internal-myappname-13718787520.us-east-1.elb.amazonaws.com:8443] in the request [/]. Check for request manipulation or third-party intercept.   ... View more

yeah. I tried that but still same issue ... View more

{ "operation": "default", "spec":{ "*" : { "flow_file_id" : "${uuid}" } } } this spec is generating the same uuid for all the objects in the array of json.  ... View more

Thanks for the reply @MattWho  Firstly with the below configurations changes in authorizers.xml, I was able to store the users and their related authorization policies in database and I was able to successfully store the users and their permissions in postgresSQL database from registry <userGroupProvider> <identifier>database-user-group-provider</identifier> <class>org.apache.nifi.registry.security.authorization.database.DatabaseUserGroupProvider</class> <property name="Initial User Identity 1">DEV-ADMIN</property> </userGroupProvider> ------------------------------ <accessPolicyProvider> <identifier>database-access-policy-provider</identifier> <class>org.apache.nifi.registry.security.authorization.database.DatabaseAccessPolicyProvider</class> <property name="User Group Provider">database-user-group-provider</property> <property name="Initial Admin Identity">DEV-ADMIN</property> <property name="NiFi Identity 1"></property> <property name="NiFi Group Name"></property> </accessPolicyProvider> -------------------------------------- <authorizer> <identifier>managed-authorizer</identifier> <class>org.apache.nifi.registry.security.authorization.StandardManagedAuthorizer</class> <property name="Access Policy Provider">database-access-policy-provider</property> </authorizer>   Everything is working perfect. the only need here is to get the existing users.xml and authorizations.xml data migrated to Postgres DB and we can get rid of these files. Please help ... View more