08-07-2012 02:15 PM
I have used the kEncrypt.sh to generate encrypted password. Then drop the first and last 3 characters (#!#) and update the password in an environment. I would like to create a workflow that will automate this. Is it possible to pass the entire encryption to the update statement or must you drop the first 3 and last 3? Because I am not sure of an easy way to drop the last 3 without some crazy awk or sed. (Plus I would prefer not to mess around with cutting characters). Any suggestions or better ways to perform this? I need to allow some users to update a few passwords in PPM.
08-07-2012 02:20 PM
We have a request type for this function. The commands that encrypt the new value and place it in a temporary token are:
./kEncrypt.sh -t "[REQD.VP.RUNTIME_PASSWORD]" | grep "\#\!\#" | sed 's/#\!#//g'
08-08-2012 12:59 PM
IT Governance Professional
& PPM Solution Architect
08-08-2012 01:54 PM
We run on AIX servers. grep and sed are also available in a Cygwin environment which, I assume, would be available on a Windows server that is running PPM.
08-10-2012 12:50 PM
That should work. Do you run an update script to update a PPM environment password or do you pass the token to a script to run?
08-13-2012 10:17 AM
We create a script with the appropriate values with ksc_begin_script / ksc_end_script, then execute it with a sqlplus command.