Passing in a DataStage encrypted password to ISD

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
BradJoss
Premium Member
Premium Member
Posts: 10
Joined: Thu Jun 04, 2009 9:37 am
Location: Winnipeg, Manitoba, Canada

Passing in a DataStage encrypted password to ISD

Post by BradJoss »

Hi All,

I'm not sure if this is the right forum but I've seen other posts that relate to this issue. If it's not please let me know and I'll move it.

So here's the problem I'm facing.

I've figured out, with help from this site (Big Thanks), that the ISDAdmin command line tool is how to change the runtime values of our DataStage job that we're exposing as a web service call in ISD. However, we don't want to have to set the encrypted fields using clear text as this violates our Security requirements. We know and have access to the encrypted password values that DataStage creates when we set those values in a Parameter Set. The problem that I'm facing is when I try to pass in the encrypted value, ISDAdmin thinks it's clear text, and encrypts it again.

Does anyone know a solution to this problem?

Thanks in advance!
Brad
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You can encrypt values using encrypt.sh (in the bin directory of ASBNode or ASBServer) and use these (for example {iisenc}s8dwdS#sf9wd1f3ssfre--) in your command line. The encrypt.sh utility uses AES-128 encryption by default (you can choose something else).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
eostic
Premium Member
Premium Member
Posts: 3838
Joined: Mon Oct 17, 2005 9:34 am

Post by eostic »

Off the top of my head, I would instead set this up as an always on job so that I don't have to pass the job parameter at all....the encrypted value will be in the app itself and each invocation will be vastly more efficient. Alternatively, consider using https and ssl for encryption of the entire soap envelope on the wire.

Ernie
Ernie Ostic

blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
Post Reply