How is the prpcutils passwords gettting encrypted while performing deployment ?
We have WebSphere WAS 7.x version connecting with DB2 V 11. We also have Pega 6.2 SP1 version deployed in the WAS. When we are trying to verify the encryption mechanism for DB2, we found that in the WAS security.xml file , we have the xor encryption enabled at the db2. However, but while doing the deployment through prprutils through the same server which is using the same DB2 user ID, we have used the plain password and its working in this case as well. Hence we would like to know how is prpcutils doing the encryption or decryption and how both a encrypted password in the earlier case and plain password in the latter case are working ?
***Edited by Moderator Marissa to update platform capability tags****
The prpcUtils command line tool is not using the application server. It starts its own version of the pega engine to run the various tools. The database connection is provided in the prpcUtils.properties file and the password in that file is in plain text. If you do not want to have an unencrypted password on the filesystem you could pass the property using the command line or provide your own versions of the prbootstrap.properties and prconfig.xml files and use the PassGen tool to encrypt the password in the prbootstrap and the generate a keyring file to include the passwords needed in prconfig.xml.
Thanks very much for your reply. I have read this in another thread but I am new to this and not pretty sure how to get this done in detail. Would you mind helping with those details or share any other forum thread that has this info.