Confirm encrypted password is set to $PROJDEF?
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 43
- Joined: Wed Feb 12, 2014 12:34 pm
- Location: Hyderabad, India
Confirm encrypted password is set to $PROJDEF?
Could you please advise is there any way to check and verify whether encrypted password in parallel job has value $PROJDEF not anything else directly through designer or is there any shortcut to verify this.
SyedMuhammadMehdi
The algorithm for encrypting within DataStage is not a complex one, so if you write a job and use $PROJDEF as a the value of an encrypted parameter that string can be used as comparison as it will always be the same encrypted value for the same input string.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 43
- Joined: Wed Feb 12, 2014 12:34 pm
- Location: Hyderabad, India
Well, we know how to fix the premium content problem.
But the answer is visible in the viewable portion. The same string will always get encoded the same way, even in different jobs. So if you know what the encrypted string for $PROJDEF looks like in one job, you can compare it with an encrypted string in another job and if the encryptions are identical then so are the source strings.
But the answer is visible in the viewable portion. The same string will always get encoded the same way, even in different jobs. So if you know what the encrypted string for $PROJDEF looks like in one job, you can compare it with an encrypted string in another job and if the encryptions are identical then so are the source strings.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 43
- Joined: Wed Feb 12, 2014 12:34 pm
- Location: Hyderabad, India
For me encrypted password is shown as ***** irrespective of what the password is.
Thanks, But this is not my query, usually what we do is when we add environment variables in our parallel job we forgot to change value of password to $PROJDEF and when we export these jobs to other enviroments that is from dev to production and when production password is different to dev password and when our job fails in production due to incorrect password there we identify that the password is not set to $PROJDEF. So, I'm searching out a simple way to identify whether password is set to $PROJDEF or not.
Thanks, But this is not my query, usually what we do is when we add environment variables in our parallel job we forgot to change value of password to $PROJDEF and when we export these jobs to other enviroments that is from dev to production and when production password is different to dev password and when our job fails in production due to incorrect password there we identify that the password is not set to $PROJDEF. So, I'm searching out a simple way to identify whether password is set to $PROJDEF or not.
SyedMuhammadMehdi
-
- Participant
- Posts: 43
- Joined: Wed Feb 12, 2014 12:34 pm
- Location: Hyderabad, India
There's an even simpler way: use the export to file function in Administrator's environment variables screen. You can temporarily create an encrypted variable, give it the "value" of $PROJDEF, and examine the exported file. Your encrypted string will be there.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
-
- Participant
- Posts: 43
- Joined: Wed Feb 12, 2014 12:34 pm
- Location: Hyderabad, India
What I found in 8.7:chulett wrote:Ah... so they've "fixed" that, good to know.
- An env var with type=Encrypted still shows the "encoded" text in the job log
- A traditional parameter (non-env var) with type=Encrypted shows only stars in the job log, so that much is fixed. You can still export the parameter set and view the encoded text.
I did open a PMR about the ease of decoding, which I'm sure was after 9.1 GA. I have yet to re-visit this in 9.1 or 9.1.2 to see the extent of improvements, if any.
Choose a job you love, and you will never have to work a day in your life. - Confucius
-
- Participant
- Posts: 43
- Joined: Wed Feb 12, 2014 12:34 pm
- Location: Hyderabad, India