I'm not sure it is in the UI, but you should be able to use the REST API to create a policy and set the resource to "/resources". I don't have an example handy, but if you looked in Chrome Dev tools while creating another policy you could see what the UI normally submits and just modify it.
Might worth exposing in the UI from the policies section of the top-right hamburger menu. On Thu, Jun 7, 2018 at 8:49 AM, Mark Bean <mark.o.b...@gmail.com> wrote: > Bryan, > > How does one get READ for /resources? Put another way, what policy > corresponds to /resources? The user has been added to all policies > available through the UI, and /resources does not appear in > authorizations.xml. > > Thanks, > -Mark > > On Thu, Jun 7, 2018 at 8:37 AM, Bryan Bende <bbe...@gmail.com> wrote: > >> 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 <mark.o.b...@gmail.com> 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 >>
