10-25-2013 07:18 AM - edited 03-01-2019 09:05 AM
Just wanted to get an idea if anyone knows if as a best practice this should be populated or not. We don't have the configuration setting 'FTP Local User Mandatory' checked, but I wonder if it should. I am assuming that if local user is not populated that the agent service account then is what the job runs as.
Solved! Go to Solution.
11-07-2013 12:52 PM
Everyones security requirements may vary.
I would suggest making it mandatory as a best practice as it forces you to be consistent. Then when that one-off happens and you need to deliver to a "secure" location the RTU id is obvious and not hidden by falling out to the agent service and a different RTU could be used that is permissioned. (we name our RTU and logon accounts for services differently)
We have very few FTP jobs left in Tidal (we have to host our own FTP Solution anyway so we just use its API to send / rec) which will all be retired when we move to 6.X
11-07-2013 12:52 PM
Everyones security requirements may vary.
I would suggest making it mandatory as a best practice as it forces you to be consistent. Then when that one-off happens and you need to deliver to a "secure" location the RTU id is obvious and not hidden by falling out to the agent service and a different RTU could be used that is permissioned. (we name our RTU and logon accounts for services differently)
We have very few FTP jobs left in Tidal (we have to host our own FTP Solution anyway so we just use its API to send / rec) which will all be retired when we move to 6.X
11-08-2013 07:38 AM
I agree for consistency sake its what I should do. its just funny how years and years go by this has never come into question, then I have one user that leaves it blank, cause he can, and how I am having this question LOL.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide