I have created a job that I sense will be useful for a lot of people in my company.
Short explained they will have the possibility to write their own sql query and execute the job that will iterate the sql over multiplte db's and deliver the merged output per Mail in an .csv file. This already work as I want to but now I need some help with finetuning.
For security reasons I want to add some kind of password protection or something and maybe you guys have some good suggestions on how to solve this.
I was thinking of something like this:
When the user executes the .batch the have to enter a password. If the password is wrong they job obviously stops. If it's correct the job continues.
A second step would be to have different passwords (users) where only the ones with admin password can run delete/update/insert statements and the rest are only allowed to run select statements. Is there some option in for example tell dbInput to only allow select statements?
I presume that this is using Talend Open Studio and they are running by clicking on the batch file or running it from the command line. Is that correct? If so, you can set up a context variable (or a couple) to take the username and password, then use it in the job to check against data stored in a database somewhere. It the information is correct, you can set the rest of the job to run. If not, then you can simply print an error message using a tLogRow.
This is incredibly basic and not what would be described as truly secure, but should meet your requirements if my assumptions are correct.
