<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Getting &amp;quot;No applicable policies could be found. Contact the system administrator.&amp;quot;  when running a curl command on a NiFi API Endpoint in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Getting-quot-No-applicable-policies-could-be-found-Contact/m-p/202327#M164333</link>
    <description>&lt;P&gt;Ok, it is interesting is that you mentioned you can put the URL in Google Chrome and get the JSON back...&lt;/P&gt;&lt;P&gt;Do you have a client certificate in your browser for NiFi?&lt;/P&gt;&lt;P&gt;In your curl examples you are using Kerberos...&lt;/P&gt;&lt;P&gt;Normally the first time you hit the UI, it exchanges the Kerberos ticket for a JWT (just like you were doing to get the token) and then it puts the JWT in local storage of your browser. On every request after that the UI code will send the Authorization header with the JWT from local storage.&lt;/P&gt;&lt;P&gt;When you put the API URL directly into your browser, none of NiFi's UI code is running, so there isn't anything that would perform the ticket exchange, and nothing that would send the Authorization header. So I wouldn't expect that to work unless you had a client certificate in your browser.&lt;/P&gt;&lt;P&gt;You may want to compare the nifi-user.log above, to one when you access the URL from Chrome to see if the requests are being made as the same identities.&lt;/P&gt;</description>
    <pubDate>Sat, 20 Jan 2018 03:09:21 GMT</pubDate>
    <dc:creator>bbende</dc:creator>
    <dc:date>2018-01-20T03:09:21Z</dc:date>
  </channel>
</rss>

