<?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: Issues with AIM Hash in Secrets Management</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316384#M350</link>
    <description>&lt;P&gt;You are using CCP. CCP only supports client certificate auth or Windows OS auth - and not application hash or path.&lt;/P&gt;</description>
    <pubDate>Thu, 26 Jan 2023 09:14:10 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2023-01-26T09:14:10Z</dc:date>
    <item>
      <title>Issues with AIM Hash</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316383#M349</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__0682J00000O9zLoQAJ.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/83719i3B565677BE47818F/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__0682J00000O9zLoQAJ.png" alt="Field_Content_versions_oct20__0682J00000O9zLoQAJ.png" /&gt;&lt;/span&gt;We have been working with trying to resolve issues in our test environment after upgrading to 12.2. One issue that has come back around is that we are trying to run psPAS (yes, we know this isn't supported by CyberArk) but it's affecting the AIM service now. We get an error that: &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"Authentication error for the AIM webservice App ID&amp;nbsp;&lt;/P&gt;&lt;P&gt;[AIMWebService]. Reason: APPAP133E Failed to verify application authentication data: Hash..."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have made sure to add the appropriate has to our applications and the AIMWebService and everywhere else we can think of but still no luck. We have even tried to recreate the hash using CyberArk's documentation with no avail.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone ran into a similar problem and can help us resolve it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance!!&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2023 20:14:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316383#M349</guid>
      <dc:creator>jdiffee</dc:creator>
      <dc:date>2023-01-25T20:14:02Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with AIM Hash</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316384#M350</link>
      <description>&lt;P&gt;You are using CCP. CCP only supports client certificate auth or Windows OS auth - and not application hash or path.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2023 09:14:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316384#M350</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-01-26T09:14:10Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with AIM Hash</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316385#M351</link>
      <description>&lt;P&gt;https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-CP/Latest/en/Content/CP%20and%20ASCP/Application-Authentication-Methods-general.htm&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2023 09:16:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316385#M351</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-01-26T09:16:38Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with AIM Hash</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316386#M352</link>
      <description>&lt;P&gt;Do you know if this was a recent change? We are still running 12.2.4 in our test environment and have been able to use the hash in the past. &lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 19:24:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316386#M352</guid>
      <dc:creator>jdiffee</dc:creator>
      <dc:date>2023-01-27T19:24:54Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with AIM Hash</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316387#M353</link>
      <description>&lt;P&gt;If you are claiming it was working ealier then check the  recomended java/.net version againts the Hashgenerartion tool.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 20:15:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316387#M353</guid>
      <dc:creator>S.Shaikh194683</dc:creator>
      <dc:date>2023-01-27T20:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with AIM Hash</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316388#M354</link>
      <description>&lt;P&gt;If you upgraded the CCP software, you need to run this step afterwards: https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-CP/Latest/en/Content/CCP/Configure_CCPWindows.htm#DefinetheCentralCredentialProviderwebservice&lt;/P&gt;</description>
      <pubDate>Sat, 28 Jan 2023 23:24:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/issues-with-aim-hash/m-p/1316388#M354</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-01-28T23:24:20Z</dc:date>
    </item>
  </channel>
</rss>

