- 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.
01-02-2024 08:16 PM
I refer to these 2 instructional links:
And I have some questions:
+ Revoke the key and recreate it
+ Update the existing key pair
I want to know the impact that occurs in the above 2 cases Revoke the key and recreate it, Update the existing key pair and What is the best choice?
Thank everyone.
01-03-2024 02:18 AM
Hi @Huy Tran ,
About CPMComponentUser , you're able to find it in file user.ini and installeruser_account :The Username of a Vault user with 'Manage Users' permissions in the Vault. This user performs the APIKeyManager operation in the Vault. You can use user administrator for installer-user
Thank
01-03-2024 02:18 AM
Hi @Huy Tran ,
About CPMComponentUser , you're able to find it in file user.ini and installeruser_account :The Username of a Vault user with 'Manage Users' permissions in the Vault. This user performs the APIKeyManager operation in the Vault. You can use user administrator for installer-user
Thank
01-03-2024 05:49 PM
Thanks Duong, can you give me more information about impact 2 way resync the API credfile for the CPM Scanner service, and do you have any suggestions on which method to choose?
01-03-2024 05:57 PM
Hi @Huy Tran ,
Note : After running command revoke, the component user will not be able to authenticate to the Vault.
The choice of which way to proceed depends on your specific problem. However, I still recommend updating the API key. Revoking it should only be carried out as a final measure.
Thank
01-03-2024 06:05 PM
Hi @Duong Trung Duong
If updating the API key will there be any impact, and if the update is not successful, will there be any problems with the system?
01-03-2024 06:12 PM
hi @Huy Tran ,
Even if it doesn't work, it will only affect CPM, which is easy to fix. If you're really concerned about the system impact, you only need to worry about the impact of components like vault, pvwa, and psm. These components directly impact the end user. CPM is just a change password component, so don't worry
Thank
01-03-2024 06:19 PM
Hi @Duong Trung Duong
I understand now, thank you for your enthusiastic support in this case, best regards.
01-03-2024 06:21 PM
Hi @Duong Trung Duong
Sorry but I forgot to ask about the link https://AddressOfThePVWAl/passwordvault/api/, should I replace it with my pvwa link?
01-03-2024 06:28 PM
hi @Huy Tran
https://AddressOfThePVWAl/passwordvault/api/
replace "AddressofthePVWA" to IP or DNS your PVWA
Thank
01-03-2024 06:30 PM
Hi @Duong Trung Duong
Ok, I have understood. Thank you so much.
01-04-2024 07:45 PM
Hi @Duong Trung Duong
Let me try to give an example, can you help me fill it in correctly?
apikeymanager.exe update -f apikey.ini -t <ABC> -u <installeruser_account> -a "https://pa.abc.com/passwordvault/api/"
About the installer_user account, do I need to change anything?
01-05-2024 01:58 AM
hi @Huy Tran ,
Is CPMComponentUse ABC? You need to find the exact name in the user.ini file. As for installeraccount, as I mentioned earlier, you can use administrator.
01-05-2024 02:09 AM
Hi @Duong Trung Duong
I'm just giving an example, if CPI Component Use is ABC then how should I fill in the apikeymanager.exe revoke -t <CPMComponentUser> -u <installeruser_account> -a command?
01-05-2024 02:22 AM
Hi @Huy Tran ,
apikeymanager.exe update -f apikey.ini -t ABC -u administrator -a "https://pa.abc.com/passwordvault/api/" something like that
01-07-2024 06:06 PM
hi @Duong Trung Duong
Thanks Duong so much.
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!

