- 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-13-2021 10:31 PM
I have read that CPM can rotate hardcoded credentials in configuration files in two ways. One is store credentials in plain text and another is store credentials in encrypted form.
I am not clear about latter one. If CPM replace credentials in configuration files with encrypted one, how can application that use that configuration files be able decrypted the credentials?
01-14-2021 12:02 AM
CPM must store the password in a form that the app can understand. If your specific app requires the password to be in clear-text, configure CPM to replace it in clear-text. If your app requires the password to be stored (for example) as a SHA256 hash, then you can configure CPM to rotate the password on the target, hash the password, and replace only the hash in the apps config file.
01-21-2021 07:17 AM
@Coveo Test Test comment
01-21-2021 12:37 PM
you have two options
1: The application is set up to do a pull command from the vault. So the application when it needs the password will reach into the vault for it the password and it is encrypted.
2: The CPM does a push command which updates the config file. this is where you run into the issue of them being unencrypted.
01-26-2021 09:36 PM
I get it. Thanks for answer!!
01-26-2021 09:42 PM
@Jason Pratt Thanks for answer!!
But I am not clear about 1st option. For 1st option to work, we need application to have an ability to pull the password. And then, application will update the config file itself. Am I right?
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!

