<?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>topic Re: CP thinks that an application pool is running under a different user and gives me an authentication error. in Secrets Management</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management/cp-thinks-that-an-application-pool-is-running-under-a-different/m-p/1391127#M1706</link>
    <description>&lt;P&gt;The error is probably right.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A quick way to double check is allow the user  in the App Hardening settings which you see in the AppAudit logs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Another destructive way would be disabled the denied user in AD &amp;amp; you get to know if that user is running the app pool or not &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Apr 2021 17:41:30 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2021-04-28T17:41:30Z</dc:date>
    <item>
      <title>CP thinks that an application pool is running under a different user and gives me an authentication error.</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/cp-thinks-that-an-application-pool-is-running-under-a-different/m-p/1391126#M1705</link>
      <description>&lt;P&gt;Hi all, &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're having this very weird issue. We have an application pool in a server that is running under "Domain\User1", there are plenty of calls daily to CyberArk with no issues, however, recently we got a few errors in which it says that the application pool is running under a different user. I checked the app pool and it is running under the right user. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is the error that we get which I've seen before when a user is unauthorized. This is not our case, the application is running under the right user which is white listed in the authentication portion of the application in CyberArk. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;APPAP002E Provider Prov_... has failed to fetch password with query [safe=samename;folder=root;object=account name; for application [application name]. Fetch reason: [Extraction of Secure String]. Failure reason:[APPAP133E Failed to verify application authentication data: OSUser "Domain\User" is unauthorized. &lt;/B&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 15:54:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/cp-thinks-that-an-application-pool-is-running-under-a-different/m-p/1391126#M1705</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-04-22T15:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: CP thinks that an application pool is running under a different user and gives me an authentication error.</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/cp-thinks-that-an-application-pool-is-running-under-a-different/m-p/1391127#M1706</link>
      <description>&lt;P&gt;The error is probably right.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A quick way to double check is allow the user  in the App Hardening settings which you see in the AppAudit logs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Another destructive way would be disabled the denied user in AD &amp;amp; you get to know if that user is running the app pool or not &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Apr 2021 17:41:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/cp-thinks-that-an-application-pool-is-running-under-a-different/m-p/1391127#M1706</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-04-28T17:41:30Z</dc:date>
    </item>
  </channel>
</rss>

