Mark, The resources end-point returns all of possible resource identifiers that can be used to create policies. If you look in authorizations.xml on the policies and see things like "/flow" or"/controller", those are examples of resources.
I'm not sure that NiFi itself uses it for anything, but it is more for external systems or scripts that may want to retrieve this information. For example, integration with Apache Ranger lets you define policies in Ranger and it needs to know the list of resources to define policies for. As far as I know, a user would need READ to /resources to make a request to the end-point. Thanks, Bryan On Thu, Jun 7, 2018 at 8:13 AM, Mark Bean <[email protected]> wrote: > What information specifically does the Rest API endpoint "/resources" > provide? > > Also, a user belongs to every policy, and when hitting that endpoint still > receives "No applicable policies could be found. Contact the system > administrator." Is the "/resources" endpoint still supported? > > Thanks, > Mark
