Issues getting a custom Plug-in for Kong to work

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Issues getting a custom Plug-in for Kong to work

L0 Member

We have created a custom plugin so we can vault Kong consumer credentials in CyberArk and have password rotations managed by CPM. The plugin will call a Kong API to update a client secret in Kong. When we test the plugin on a developer machine it works. When we test it from CPM we see the below log entries. Since we don't need CPM to login to a remote machine, how can we configure the platform to turn that off. This is an API integration and the plugin just needs the values passed by CPM and it will update the secret in Kong.:

 

Logs:

23/01/2025 13:54:25 [1294] CACPM175I Immediate Searches: Searching for passwords for policy Policy-KongOauthAPI.ini (ID KongOauthAPI).

23/01/2025 13:54:25 [1294] CACPM353I Performing failure and immediate search for policy Policy-KongOauthAPI.ini (ID KongOauthAPI).

23/01/2025 13:54:25 [1294] CACPM114I Immediate Searches: Found 1 passwords for policy Policy-KongOauthAPI.ini (ID KongOauthAPI).

23/01/2025 13:54:25 [1294] CACPM321I Performing coordination phase for policy Policy-KongOauthAPI.ini (ID KongOauthAPI).

23/01/2025 13:54:25 [1294] CACPM322I Executing password tasks handlers for policy Policy-KongOauthAPI.ini (ID KongOauthAPI). 1 passwords to handle.

23/01/2025 13:54:25 [1294] CACPM115I Wait for Password Handler(s) to end.

 

23/01/2025 13:54:25 [20f0] CACPM088I Starting Password Handler (Safe name:KongDevSafe, Folder name:Root, Object name: Application-KongOauthAPI, Find reason: ResetImmediately).

23/01/2025 13:54:25 [20f0] CACPM252I Password details: Safe: KongDevSafe, Folder: Root, Object: Application-KongOauthAPI, Username: , Address: .

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).

 

23/01/2025 13:55:00 [20f0] CACPM072E Login process on remote machine failed (Error: 1016, Safe: KongDevSafe, Folder: Root, Object: Application-KongOauthAPI).

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).

23/01/2025 13:55:00 [20f0] CACPM099I Ending Password Handler (Safe name:KongDevSafe, Folder name:Root, Object name: Application-KongOauthAPI).

23/01/2025 13:55:00 [1294] CACPM326I Finished executing password tasks handlers for policy Policy-KongOauthAPI.ini (ID KongOauthAPI).

 

3 REPLIES 3

L5 Sessionator

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.

L0 Member

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.

L0 Member

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.

 

DllName=Custom Plugin File Name.dll

ExeName=CANetPluginInvoker.exe

 

  • 226 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!