Why does change password prompt a logon action in TPC?

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

Why does change password prompt a logon action in TPC?

L1 Bithead

I have an account which I am trying to manage using a prompt and a process file with the TPC. Verify completes successfully, however, every time I try to change the password (by clicking "Change the password now by the CPM" in the PVWA), the action that is triggered is logon and not changepass. Because of this pmnewpass is never populated and the script errors out for trying to set a blank new password. What is causing the action to be logon and not changepass?

1 accepted solution

Accepted Solutions

The documentation on testing a CPM plugin should give some insight on what the CPM is doing. It is running the 'logon' action first and then the 'changepass' action -- both using the prompts and process files you defined.

 

In the Prompts file, you should see a prompt with an expression that checks the action type. Something like

ActionIsLogon=(expression)[string equal -nocase "<action>" "logon"]

which is used as part of a transition to perform what is necessary to logon steps. After it hits an END state, then the CPM will run again where the action this time is changepass.

 

View solution in original post

5 REPLIES 5

L3 Networker

hi @Nathaniel Chiles​ ,

This is process change password :

Field_Content_versions_oct20__068Ht00000QdBgjIAF.pngIt mean , when you click change password , it will use this credential login to target, after that type command change password, maybe your target use another command change password so this is reason why you can't change password. You can you PGU to customize plugin for CPM

https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PCP/PGU-introduction.htm?TocPath=Developer%7CCreate%20extensions%7CPlugin%20Generator%20Utility%7C_____0

To add to this: the change process is made up of two actions: logon and changepass. Logon is executed first to see if the credentials in the Vault match what’s in the target system and after a successful logon action, the CPM generates a new password that is used as the value for pmnewpass. Only in the changepass action does pmnewpass have a value.

Thank you for that information. I reviewed some of the existing prompt and process files and I do not see an explicit reference to switching from logon to changepass. When does this occur or what is the command to confirm to CyberArk the initial logon process completed successfully and to move into the changepass action?

The documentation on testing a CPM plugin should give some insight on what the CPM is doing. It is running the 'logon' action first and then the 'changepass' action -- both using the prompts and process files you defined.

 

In the Prompts file, you should see a prompt with an expression that checks the action type. Something like

ActionIsLogon=(expression)[string equal -nocase "<action>" "logon"]

which is used as part of a transition to perform what is necessary to logon steps. After it hits an END state, then the CPM will run again where the action this time is changepass.

 

And that is the is part I was missing. To make it abundantly clear to anyone reading this in the future. When changing the password, CyberArk will go through the script twice. First using the action of logon and then using the action of changepass. To reach the second state, the script must successfully complete a chain of states and hit an END. For mine, I had a check for an action of logon that was then routed down the same path as Verify. On the second pass through the script, the action was not changepass and instead of taking the verify/logon path it took the changepass path and completed successfully. Thank you for helping me with that.

  • 1 accepted solution
  • 850 Views
  • 5 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!