@alexwillmer  NiFi does not support using wildcards in all scenarios. Access decisions would include authorization against specific endpoints.  Not access decisions that may not work with wildcards may include some buttons remaining greyed out. So if you encounter a NiFi Resource Identifier is not giving you the expected result with a wildcard, try setting the policy explicitly and see if desired outcome is observed.  The following article provides insight in to the expected access provided by each NiFi Resource Identifier: https://community.cloudera.com/t5/Community-Articles/NiFi-Ranger-based-policy-descriptions/ta-p/246586 NiFi actually downloads the policy definitions from Ranger and all authorizations are done based on the last downloaded set of policies (NiFi runs a background thread to check for updated policy definitions from Ranger).  NiFi does not send a request to verify authorization to Ranger itself. Hope this helps, Matt ... View more

Hi @Alex Willmer, No The Third Result is not exepcted, Ideally when you shutdown and restart the ambari-agent host , and ambari-agent was started the expectation is ambari-agent starting all the services automatically. Can you please confirm what was the state of services of that host before the shutdown, if the state of service was already stopped ambari-agent will retain the state or else ambari-agent will try to start it. you can know it by checking the ambari-server logs after start of ambari-agent, you will find some logs like this : ambari-server/ambari-server.log:70978:14 Jan 2019 15:25:41,690 INFO [qtp-ambari-agent-1082725] HeartBeatHandler:464 - Recovery configuration set to RecoveryConfig{, type=AUTO_START, maxCount=6, windowInMinutes=60, retryGap=5, maxLifetimeCount=1024, components=METRICS_MONITOR,HBASE_REGIONSERVER,DATANODE,KAFKA_BROKER,LOGSEARCH_LOGFEEDER,HST_AGENT,SUPERVISOR,NODEMANAGER, recoveryTimestamp=1547450741689} also something like this in ambari-agent HW15603:ambari-agent asnaik$ grep -nir 'RecoveryManager' * |grep -i 'current status is set to STARTED'  ambari-agent.log:48593:INFO 2019-01-14 15:25:47,412 RecoveryManager.py:185 - current status is set to STARTED for HST_AGENT  ambari-agent.log:48751:INFO 2019-01-14 15:27:15,042 RecoveryManager.py:185 - current status is set to STARTED for METRICS_MONITOR  ambari-agent.log:48757:INFO 2019-01-14 15:27:34,098 RecoveryManager.py:185 - current status is set to STARTED for HBASE_REGIONSERVER  ambari-agent.log:48851:INFO 2019-01-14 15:28:29,509 RecoveryManager.py:185 - current status is set to STARTED for LOGSEARCH_LOGFEEDER  ambari-agent.log:48899:INFO 2019-01-14 15:29:06,880 RecoveryManager.py:185 - current status is set to STARTED for NODEMANAGER Hop this helps you troubleshoot more on this. ... View more