<?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: Kerberos NiFi API PUT request fails identifying user in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Kerberos-NiFi-API-PUT-request-fails-identifying-user/m-p/367304#M239864</link>
    <description>&lt;P&gt;I'm just realized that I was writting Authorization without the "h" in the PUT request! &lt;span class="lia-unicode-emoji" title=":sad_but_relieved_face:"&gt;😥&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Problem solved&lt;/P&gt;</description>
    <pubDate>Thu, 30 Mar 2023 12:08:06 GMT</pubDate>
    <dc:creator>jorgeoa</dc:creator>
    <dc:date>2023-03-30T12:08:06Z</dc:date>
    <item>
      <title>Kerberos NiFi API PUT request fails identifying user</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Kerberos-NiFi-API-PUT-request-fails-identifying-user/m-p/367258#M239838</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to start/stop a processor using the NiFi API in a kerberized NiFi cluster (Cloudera Data Flow) but the PUT request to do it fails in identifying the authenticated user. Other requests like get processor information, get current user information, etc. works fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm running the process in a bash script in the same machine as the NiFi node. I have just one node in this environment with load balancer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the process I follow:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Create kerberos token in the system (kinit my.username)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. Create NiFi token calling the /access/kerberos endpoint&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;curl -k -X POST --negotiate -u : "https://node-ip:8443/nifi-api/access/kerberos"​&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3.Store the token in a variable and check I'm authenticated&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;curl -k --header "Authorization: Bearer $token" "https://node-ip:8443/nifi-api/access"                        {"accessStatus":{"identity":"my.username","status":"ACTIVE","message":"Access Granted: Token authenticated."}}​&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;4.Get processor information -&amp;gt; OK&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;curl -k --header "Authorization: Bearer $token" "https://node-ip:8443/nifi-api/processors/1e4ebf99-0181-1000-0000-000063a3fcd5"​&lt;/LI-CODE&gt;&lt;P&gt;nifi-user.log&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;2023-03-30 08:35:04,316 INFO [NiFi Web Server-20] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started node-ip [&amp;lt;my.username&amp;gt;&amp;lt;CN=node-host, O=Default Company Ltd, L=Default City, C=XX&amp;gt;] GET https://node-host:8443/nifi-api/processors/1e4ebf99-0181-1000-0000-000063a3fcd5
2023-03-30 08:35:04,318 INFO [NiFi Web Server-20] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [my.username] node-ip GET https://node-host:8443/nifi-api/processors/1e4ebf99-0181-1000-0000-000063a3fcd5​&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;5. PUT to stop de processor -&amp;gt; Fails&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;curl -k -X PUT --header "Autorization: Bearer $token" -H 'Content-Type: application/json' -H 'Accept: application/json' --data '{"revision":{"version":0,"clientId":"2be2965c-0187-1000-ae7e-fa5be1baf085"},"state":"STOPPED"}' "https://node-ip:8443/nifi-api/processors/1e4ebf99-0181-1000-0000-000063a3fcd5/run-status"​&lt;/LI-CODE&gt;&lt;P&gt;nifi-user.log&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;2023-03-30 08:44:09,318 INFO [NiFi Web Server-46774] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started node-ip [&amp;lt;anonymous&amp;gt;] PUT https://node-ip:8443/nifi-api/processors/1e4ebf99-0181-1000-0000-000063a3fcd5/run-status
2023-03-30 08:44:09,318 INFO [NiFi Web Server-46774] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [anonymous] node-ip PUT https://node-ip:8443/nifi-api/processors/1e4ebf99-0181-1000-0000-000063a3fcd5/run-status
2023-03-30 08:44:09,323 INFO [NiFi Web Server-46778] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started node-ip [&amp;lt;&amp;gt;&amp;lt;CN=node-host, O=Default Company Ltd, L=Default City, C=XX&amp;gt;] PUT https://node-host:8443/nifi-api/processors/1e4ebf99-0181-1000-0000-000063a3fcd5/run-status
2023-03-30 08:44:09,325 INFO [NiFi Web Server-46778] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [anonymous] node-ip PUT https://node-host:8443/nifi-api/processors/1e4ebf99-0181-1000-0000-000063a3fcd5/run-status
2023-03-30 08:44:09,338 INFO [NiFi Web Server-46776] o.a.n.w.s.NiFiAuthenticationFilter Authentication Started node-ip [&amp;lt;&amp;gt;&amp;lt;CN=node-host, O=Default Company Ltd, L=Default City, C=XX&amp;gt;] PUT https://node-host:8443/nifi-api/processors/1e4ebf99-0181-1000-0000-000063a3fcd5/run-status
2023-03-30 08:44:09,340 INFO [NiFi Web Server-46776] o.a.n.w.s.NiFiAuthenticationFilter Authentication Success [anonymous] node-ip PUT https://node-host:8443/nifi-api/processors/1e4ebf99-0181-1000-0000-000063a3fcd5/run-status​&lt;/LI-CODE&gt;&lt;P&gt;curl returned error&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Node node-host:8443 is unable to fulfill this request due to: No applicable policies could be found. Contact the system administrator.​&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As you can see, in the PUT request the username appears as "anonymous" instead of "my.username". Ranger audit logs show same info: username anonymous instead of my.username so the request is denied.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could anyone give me some recomendation to troubleshoot this case?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Of course, same username works perfectly in the NiFi GUI&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you very much!&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 07:16:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Kerberos-NiFi-API-PUT-request-fails-identifying-user/m-p/367258#M239838</guid>
      <dc:creator>jorgeoa</dc:creator>
      <dc:date>2026-04-21T07:16:47Z</dc:date>
    </item>
    <item>
      <title>Re: Kerberos NiFi API PUT request fails identifying user</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Kerberos-NiFi-API-PUT-request-fails-identifying-user/m-p/367304#M239864</link>
      <description>&lt;P&gt;I'm just realized that I was writting Authorization without the "h" in the PUT request! &lt;span class="lia-unicode-emoji" title=":sad_but_relieved_face:"&gt;😥&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Problem solved&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2023 12:08:06 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Kerberos-NiFi-API-PUT-request-fails-identifying-user/m-p/367304#M239864</guid>
      <dc:creator>jorgeoa</dc:creator>
      <dc:date>2023-03-30T12:08:06Z</dc:date>
    </item>
  </channel>
</rss>

