- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
04-14-2021 02:39 PM
We have the need to manage a secret that involves custom scripts (powershell). The challenge I am facing here is that this app does not accept a new password that is given, the password HAS to be generated by the app itself and then sent back to Cyberark. The script I created follows this flow:
1) you click change in cyberark
2) script runs some commands to generate a new password
3) script runs some CyberarkAPIs to put the new password into the account
The problem I am facing is that all the steps run without any issues, but then Cyberark overwrites the password at the end of the process. How do I stop this from happening?
04-15-2021 07:23 AM
hey @Vadim Melamed
It sounds like you'd want to not involve the cpm - since the password change isn't occurring from the Cyberark side but rather the target.
-Matt
04-15-2021 07:28 AM
@Matt Jennison That sounds about right. But I would still want the actions to be triggered by Cyberark (clicking change/reconcile or through some schedule)...is this possible?
04-15-2021 07:33 AM
hey @Vadim Melamed
maybe, but you'd need to discuss it with the Cyberark Extensions Dev team. It sounds like what you want will need to be a custom plug-in, if it's at all possible.
-Matt
04-15-2021 08:39 AM
It sounds like some simple cli calls. You can modify a Prompt/Process.ini file to fit your case.
I think in the docs there are some examples and instructions on how to write custom plugins.
04-15-2021 08:44 AM
I am using the powershell plugin, and it doesnt seem to be using any prompts/process files, I was hoping it was because that would have been an easy fix
04-15-2021 09:07 AM
What kind of PowerShell plugin? How does your platform look like?
04-15-2021 09:27 AM
Powershell plugin: PowershellPlugin.exe
actually while I was getting details of the platform I did find a prompts policy file that I guess I missed previously. Assuming its a regular platform, how would you go about removing the generation of <pmnewpass> ?
I see the following lines:
SendNewPass=<pmnewpass> #which can probably be removed
and in the states, i see these lines:
StartScript, NewPassword, SendNewPass
SendNewPass, LogonPassword, SendLogonPass
#which i can probably edit the first like to something like this:
StartScript, LogonPassword, SendLogonPass
04-16-2021 12:49 AM
oh right, you would need a non-CPM generated password there. I'm not aware of a method to overwrite that value, although the process could have it as environment variable or so.
I could think of a method, but it is ultra homebrew:
Let the CPM change be successful > Let the plugin generate a Windows event > WinEvent triggers another PS script which changes the password on the target system, gets that password and via PVWA API updates the target account in CyberArk.
The main idea is to make a process which updates the password of the target account in CyberArk based on what was generated in the App.
I would but look a bit more, it is a bit confusing that you cannot specify passwords in the target app. Reconciliation does not work either?
04-16-2021 08:35 PM
Ultra homebrew is where I live haha. I found a temporary workaround utilizing the Service Account Platforms, or "usages". Thanks for the ideas though!
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!

