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

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

@Meeran  Sharing the full exception that was output when you tried to import key maybe helpful, But I am also not sure why you are trying to add a Client private key to your AWS load-balancer? I am not well versed on AWS load balancer configuration, so helping you get past your LB setup/configuration issue may be difficult for me.  I do know TLS very well and explained the meaning of the two TLS exceptions you encountered.    The HTTPS LB exception could be resolved by making sure the TrustedCertEntry(s) for the complete trust chain for the HTTPS LB's privateKey are present in the NiFi-Registry's truststore.jks.  You should also add the trustedcertEntry for the NiFi CA you appeared to be using to the truststore used by your HTTPS LB. Thank you, Matt ... View more