@johannes_meixne    The only place you would use "{0}" would be in the ldap-provider used for user authentication.  The {0} gets replaced with the username entered in the login UI.  The LdapUserGroupProvider however is used by the nifi authorizer to assemble a list of users and group strings (along with the association/membership between those user and groups) which can be used to assign authorizations against.  The LdapUserGroupProvider executes on NiFi startup and then on a configured schedule to refresh the synced users and groups.  Since it takes no input you can not use "{0}" in the search filter. ... View more

Yes. One of the processor inside processor group is using that variable. The variable is not exported but the value of the property is showing as ${'var'}. I am able to change the value using env variable. ... View more

I'm not sure if this helps but, below is a sample nginx configuration that worked for me. I didn't need the X-ProxyContextPath but t, my requests are still context root of "/nifi". I suspect I'd need the X-ProxyContextPath if my requests were something like, <my-site>/nifi location /nifi { proxy_pass http://<nifi-ip/dns-name>:<nifi-port>/nifi; proxy_set_header 'X-ProxyScheme' 'http'; # proxy_set_header 'X-ProxyHost' '<external-proxy-ip>'; proxy_set_header 'X-ProxyPort' '<proxy-ip>'; } ... View more

Just In case !! https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.1.1/bk_user-guide/content/Controller_Services_for_Dataflows.html ... View more

I'm surprised it wasn't @bbende@hortonworks.com who wrote this article 😉 ... View more