Linux password VS DataStage Client password
Posted: Thu Jul 09, 2015 12:50 pm
Currently our application ID/password to log into DataStage Client/Director are the SAME as for the Linux server.
For this example: ID: xyzops password: PASS123
Our jobs run thru a mainframe scheduler with ID xyzops using a common shell script to build the dsjob command. We are using a credentials file to pass to dsjobs and the password 'PASS123' is encrypted. (Changed as per Auditing).
A developer can log into the Client with this ID and password but the project is read-only (on purpose, Production)
But, they can log into the Linux OS, switch user with this ID and Password and now be able to edit files (not always needed or wanted)
Can I change the Linux password to something else to prevent developers from editing without impacting DataStage? Meaning can the passwords be different?
Thank You for your time
For this example: ID: xyzops password: PASS123
Our jobs run thru a mainframe scheduler with ID xyzops using a common shell script to build the dsjob command. We are using a credentials file to pass to dsjobs and the password 'PASS123' is encrypted. (Changed as per Auditing).
A developer can log into the Client with this ID and password but the project is read-only (on purpose, Production)
But, they can log into the Linux OS, switch user with this ID and Password and now be able to edit files (not always needed or wanted)
Can I change the Linux password to something else to prevent developers from editing without impacting DataStage? Meaning can the passwords be different?
Thank You for your time