<?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>article AAM Provider 12.1 And SDK 2 Compatibility Issues in Secrets Management Articles</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management-articles/aam-provider-12-1-and-sdk-2-compatibility-issues/ta-p/1427760</link>
    <description>In response to a security finding AAM Provider SDK's will need to be updates when upgrading provider to or above 12.1

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;Due to a security vulnerability the communication channel between AAM SDK’s and AAM providers was updated in version 12.1. This new SDK version can be referred to as “SDK 2”. This change breaks previous compatibility where SDK’s did not need to be updated when providers were upgraded. (this had been a longstanding best practice)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="line-height: normal;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="color: #181818;"&gt;12.1 and higher compatibility&lt;/SPAN&gt;&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Moving forward providers 12.1 and higher will be compatible with “SDK 2” meaning that if the integration has an SDK version 12.1 or above it will be compatible with other providers that are 12.1 and above.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Central Credential Provider&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;The CCP is also affected by the SDK change but will not effect the web based SOAP or REST API’s. It is recommended to only install the version of the provider that comes packaged with the CCP web application. Using the paired Provider and Web Application packages will avoid any SDK conflicts.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Resolution&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Identify how the application making AAM calls consumes the SDK files and provide the new compatible version. Some applications will load SDK files from the default install location. In this case upgrading the provider will update the SDK files as well.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Other applications may have specific instructions to update the SDK files or require a developer to update their package to include the new SDK file.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Idira Support will not be able to determine how each integrated application consumes their SDK files. This is the responsibility of the application or integration owner to document and own.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Where Can SDK Files Be Found After Installation or Upgrade&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;Windows&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;C:\Program Files (x86)\CyberArk\ApplicationPasswordSdk&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;(On Windows this path could be on any drive)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;Unix&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="font-family: &amp;quot;Arial&amp;quot;,sans-serif;"&gt;&lt;SPAN style="color: black;"&gt;/opt/CARKaim/sdk&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;B&gt;Error Messages Generated When An Incompatible SDK Calls A 12.1+ New Provider&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;APPAP009E Application Password Provider exception occurred. APPAP381E SDK Protocol version is not supported, Please use the updated version (Codes: -1, -1)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;APPAP300E Failed to retrieve encryption and decryption information&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;</description>
    <pubDate>Thu, 05 Nov 2026 20:08:53 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T20:08:53Z</dc:date>
    <item>
      <title>AAM Provider 12.1 And SDK 2 Compatibility Issues</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management-articles/aam-provider-12-1-and-sdk-2-compatibility-issues/ta-p/1427760</link>
      <description>In response to a security finding AAM Provider SDK's will need to be updates when upgrading provider to or above 12.1

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;Due to a security vulnerability the communication channel between AAM SDK’s and AAM providers was updated in version 12.1. This new SDK version can be referred to as “SDK 2”. This change breaks previous compatibility where SDK’s did not need to be updated when providers were upgraded. (this had been a longstanding best practice)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="line-height: normal;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="color: #181818;"&gt;12.1 and higher compatibility&lt;/SPAN&gt;&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Moving forward providers 12.1 and higher will be compatible with “SDK 2” meaning that if the integration has an SDK version 12.1 or above it will be compatible with other providers that are 12.1 and above.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Central Credential Provider&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;The CCP is also affected by the SDK change but will not effect the web based SOAP or REST API’s. It is recommended to only install the version of the provider that comes packaged with the CCP web application. Using the paired Provider and Web Application packages will avoid any SDK conflicts.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Resolution&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Identify how the application making AAM calls consumes the SDK files and provide the new compatible version. Some applications will load SDK files from the default install location. In this case upgrading the provider will update the SDK files as well.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Other applications may have specific instructions to update the SDK files or require a developer to update their package to include the new SDK file.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Idira Support will not be able to determine how each integrated application consumes their SDK files. This is the responsibility of the application or integration owner to document and own.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="color: #181818;"&gt;Where Can SDK Files Be Found After Installation or Upgrade&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;Windows&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;C:\Program Files (x86)\CyberArk\ApplicationPasswordSdk&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;(On Windows this path could be on any drive)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;Unix&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;SPAN style="background: white;"&gt;&lt;SPAN style="font-family: &amp;quot;Arial&amp;quot;,sans-serif;"&gt;&lt;SPAN style="color: black;"&gt;/opt/CARKaim/sdk&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;&lt;B&gt;Error Messages Generated When An Incompatible SDK Calls A 12.1+ New Provider&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;APPAP009E Application Password Provider exception occurred. APPAP381E SDK Protocol version is not supported, Please use the updated version (Codes: -1, -1)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: Calibri,sans-serif;"&gt;APPAP300E Failed to retrieve encryption and decryption information&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;</description>
      <pubDate>Thu, 05 Nov 2026 20:08:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management-articles/aam-provider-12-1-and-sdk-2-compatibility-issues/ta-p/1427760</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T20:08:53Z</dc:date>
    </item>
  </channel>
</rss>

