Gurus,
I'm working in DS 7.5 and for some reasons $PROJDEF do not work for encrypted password but if I make the password as string instead of encrypted it works.
Any suggestion , I read before that this is a bug but is there is any patch available for it.
Rgds,
$PROJDEF
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Hi,
At my last site, I was on 7.5.1 and $PROJDEF did work successfully for encrypted passwords.
I'm not sure whether there is a patch for it. What do the product support people say?
Thanks,
Naveen.
At my last site, I was on 7.5.1 and $PROJDEF did work successfully for encrypted passwords.
I'm not sure whether there is a patch for it. What do the product support people say?
Thanks,
Naveen.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
-
- Participant
- Posts: 437
- Joined: Fri Oct 21, 2005 10:00 pm
I'm using it right now. How are you populating the default value? When I am putting it into the job properties I am copying and pasting it in from other variables.
Keith Williams
keith@peacefieldinc.com
keith@peacefieldinc.com
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
It should work but it can be difficult to get right and to migrate through environments. As KW suggests always go with the copy and paste of the password value from something like notepad rather then trying to type it in manually.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
-
- Premium Member
- Posts: 252
- Joined: Mon Sep 19, 2005 10:28 pm
- Location: Melbourne, Australia
- Contact:
We had the same problem on 7.5. I don't recall how it was fixed exactly, but I think it was this:
We created the variables initially as STRING in Administrator and changed them to ENCRYPTED after having included them in a number of jobs (which stopped working). To fix it, we may have removed the variables as parameters of all jobs and then included them back in.
To find out what the Job thinks the value is, use a Transformer to map the encrypted variable to a column in a file. Run the job and look at the file. If all is well, the correct un-encrypted value should display (bit of a security problem, but a usefult feature at times).
We created the variables initially as STRING in Administrator and changed them to ENCRYPTED after having included them in a number of jobs (which stopped working). To fix it, we may have removed the variables as parameters of all jobs and then included them back in.
To find out what the Job thinks the value is, use a Transformer to map the encrypted variable to a column in a file. Run the job and look at the file. If all is well, the correct un-encrypted value should display (bit of a security problem, but a usefult feature at times).
Ross Leishman
Re: $PROJDEF
Mistake at my end the version is 7.1 and somehow it do not accept $pojdef for encrypted password, if I type the correct password in encrypted form it works but if I default it to $PROJDEF it fails,
Thanks,
Munish
Thanks,
Munish
shrey3a wrote:Gurus,
I'm working in DS 7.5 and for some reasons $PROJDEF do not work for encrypted password but if I make the password as string instead of encrypted it works.
Any suggestion , I read before that this is a bug but is there is any patch available for it.
Rgds,