OK, and for the same reason you would not be able to do it from WinSCP.

martin wrote:

I assume you need to enter a password for the su command, right?

correct.

martin wrote:

Did you try to automate this with plink and WinSCP scripting? I assume you need to enter a password for the su command, right?

no.
I don't think you can login as one user and switch to other user with out prompting password. And the su command don't have password as a parameter.
So when I do it gives error msg "standard in must be a tty"

Did you try to automate this with plink and WinSCP scripting? I assume you need to enter a password for the su command, right?

First of all thanks for WinSCP. As I am more familiar with WinSCP, I use it religiously even though my company provide another proprietary SCP client application.

In my work place, we can access our RedHat Linux system with our userid (authentication controlled by Microsoft Active Directory) or by a generic application user id.
We run all the web apps using app user id, and the application files and directories are under the ownership of app user id.
To copy files from windows to Linux app dirs we login with app user id in WinSCP.

But after the Target department store security breach they are restricting many facilities.
They are removing remote login access for app user id.
We have to login using MS-AD userid, then do su app user id.
This works for PuTTY, but not for WinSCP ( https://beta.winscp.net/eng/docs/faq_su )
As well as my uid is not in the sudoers.

Along with this is another problem, we are unable to do chown or chgrp for files with my id or app user id.
But I can do chmod with my MS-AD user id or app user id for files with respective ownership.