<?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 getting a custom Plug-in for Kong to work in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/issues-getting-a-custom-plug-in-for-kong-to-work/m-p/1412598#M85456</link>
    <description>&lt;P&gt;How can we configure the plugin platform so that CPM does not try to login to Kong?  The plugin will push the new password to Kong by calling a Kong API and authenticate to the API with a token.  There is no need for CPM to login.  The plugin actions (verify and change) work fine when testing from a developer machine.&lt;/P&gt;</description>
    <pubDate>Mon, 27 Jan 2025 13:59:49 GMT</pubDate>
    <dc:creator>RSmithEB</dc:creator>
    <dc:date>2025-01-27T13:59:49Z</dc:date>
    <item>
      <title>Issues getting a custom Plug-in for Kong to work</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/issues-getting-a-custom-plug-in-for-kong-to-work/m-p/1412596#M85454</link>
      <description>&lt;P&gt;We have created a custom plugin so we can vault Kong consumer credentials in CyberArk and have password rotations managed by CPM.&amp;nbsp;The plugin will call a Kong API to update a client secret in Kong.&amp;nbsp;When we test the plugin on a developer machine it works.&amp;nbsp;When we test it from CPM we see the below log entries.&amp;nbsp;Since we don't need CPM to login to a remote machine, how can we configure the platform to turn that off.&amp;nbsp;This is an API integration and the plugin just needs the values passed by CPM and it will update the secret in Kong.:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Logs:&lt;/P&gt;&lt;P&gt;23/01/2025 13:54:25 [1294] CACPM175I Immediate Searches: Searching for passwords for policy Policy-KongOauthAPI.ini (ID KongOauthAPI).&lt;/P&gt;&lt;P&gt;23/01/2025 13:54:25 [1294] CACPM353I Performing failure and immediate search for policy Policy-KongOauthAPI.ini (ID KongOauthAPI).&lt;/P&gt;&lt;P&gt;23/01/2025 13:54:25 [1294] CACPM114I Immediate Searches: Found 1 passwords for policy Policy-KongOauthAPI.ini (ID KongOauthAPI).&lt;/P&gt;&lt;P&gt;23/01/2025 13:54:25 [1294] CACPM321I Performing coordination phase for policy Policy-KongOauthAPI.ini (ID KongOauthAPI).&lt;/P&gt;&lt;P&gt;23/01/2025 13:54:25 [1294] CACPM322I Executing password tasks handlers for policy Policy-KongOauthAPI.ini (ID KongOauthAPI). 1 passwords to handle.&lt;/P&gt;&lt;P&gt;23/01/2025 13:54:25 [1294] CACPM115I Wait for Password Handler(s) to end.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;23/01/2025 13:54:25 [20f0] CACPM088I Starting Password Handler (Safe name:KongDevSafe, Folder name:Root, Object name: Application-KongOauthAPI, Find reason: ResetImmediately).&lt;/P&gt;&lt;P&gt;23/01/2025 13:54:25 [20f0] CACPM252I Password details: Safe: KongDevSafe, Folder: Root, Object: Application-KongOauthAPI, Username: , Address: .&lt;/P&gt;&lt;P&gt;23/01/2025 13:54:25 [20f0] CACPM096I Creating XML file for password handler process (C:\Program Files (x86)\CyberArk\Password Manager\tmp\KongOauthAPI-KongDevSafe-Root-Application-KongOauthAPI-01-23-25 13-54-25.xml).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;23/01/2025 13:55:00 [20f0] CACPM072E Login process on remote machine failed (Error: 1016, Safe: KongDevSafe, Folder: Root, Object: Application-KongOauthAPI).&lt;/P&gt;&lt;P&gt;23/01/2025 13:55:00 [20f0] CACPM250E Operation on remote machine on password object Safe: KongDevSafe, Folder: Root, Object: Application-KongOauthAPI failed (try #0) with the following error: CACPM072E Login process on remote machine failed (Error: 1016, Safe: KongDevSafe, Folder: Root, Object: Application-KongOauthAPI).&lt;/P&gt;&lt;P&gt;23/01/2025 13:55:00 [20f0] CACPM099I Ending Password Handler (Safe name:KongDevSafe, Folder name:Root, Object name: Application-KongOauthAPI).&lt;/P&gt;&lt;P&gt;23/01/2025 13:55:00 [1294] CACPM326I Finished executing password tasks handlers for policy Policy-KongOauthAPI.ini (ID KongOauthAPI).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jan 2025 14:55:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/issues-getting-a-custom-plug-in-for-kong-to-work/m-p/1412596#M85454</guid>
      <dc:creator>TundeSomade</dc:creator>
      <dc:date>2025-01-24T14:55:33Z</dc:date>
    </item>
    <item>
      <title>Re: Issues getting a custom Plug-in for Kong to work</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/issues-getting-a-custom-plug-in-for-kong-to-work/m-p/1412597#M85455</link>
      <description>&lt;P&gt;Your logs says that the plugin you created for Kong using API could not even login from CPM to Kong. I would suggest to use powershell scripts to test login and changing password to Kong using API directly from CPM. If you get sucess, then use those powershell scripts in your process.ini file providing logic to change and verify password. &lt;/P&gt;</description>
      <pubDate>Sat, 25 Jan 2025 17:13:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/issues-getting-a-custom-plug-in-for-kong-to-work/m-p/1412597#M85455</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2025-01-25T17:13:28Z</dc:date>
    </item>
    <item>
      <title>Re: Issues getting a custom Plug-in for Kong to work</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/issues-getting-a-custom-plug-in-for-kong-to-work/m-p/1412598#M85456</link>
      <description>&lt;P&gt;How can we configure the plugin platform so that CPM does not try to login to Kong?  The plugin will push the new password to Kong by calling a Kong API and authenticate to the API with a token.  There is no need for CPM to login.  The plugin actions (verify and change) work fine when testing from a developer machine.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Jan 2025 13:59:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/issues-getting-a-custom-plug-in-for-kong-to-work/m-p/1412598#M85456</guid>
      <dc:creator>RSmithEB</dc:creator>
      <dc:date>2025-01-27T13:59:49Z</dc:date>
    </item>
    <item>
      <title>Re: Issues getting a custom Plug-in for Kong to work</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/issues-getting-a-custom-plug-in-for-kong-to-work/m-p/1412599#M85457</link>
      <description>&lt;P&gt;The plugin was developed with the Credentials Management .NET SDK.  When it was deployed to a CPM server, the platform INI file was missing the EXE name.  When that was fixed the plugin worked.  These 2 lines should be in the INI file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DllName=&lt;I&gt;&lt;U&gt;Custom Plugin File Name&lt;/U&gt;&lt;/I&gt;.dll&lt;/P&gt;&lt;P&gt;ExeName=CANetPluginInvoker.exe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 18:18:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/issues-getting-a-custom-plug-in-for-kong-to-work/m-p/1412599#M85457</guid>
      <dc:creator>RSmithEB</dc:creator>
      <dc:date>2025-04-04T18:18:17Z</dc:date>
    </item>
  </channel>
</rss>

