nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Perl file tests not working with impersonation

Kevin Butcher

TS 6.7.2
Windows 2003 SP2

We are having a problem in our workflow where Perl file tests (-d, -e, -f, etc.)are not working correctly when running as a user. If I run the script from the server it works with no issues. It also work if I make a change in the iw.cfg to include disable_ext_task_impersonation=true. Any ideas on how I can get this to work without having to disable impersonation?

Find more posts tagged with

Comments

Adam Stoller

TS 6.7.2
Windows 2003 SP2

We are having a problem in our workflow where Perl file tests (-d, -e, -f, etc.)are not working correctly when running as a user. If I run the script from the server it works with no issues. It also work if I make a change in the iw.cfg to include disable_ext_task_impersonation=true. Any ideas on how I can get this to work without having to disable impersonation?

Is this a command-line script or a CGI script?
For CGI scripts, the general procedure is to put your script directly within

IWHOME/httpd/iw-bin

and reference it as

/iw-bin/iw_cgi_wrapper.cgi/script_name

You could try the same thing for a command-line script but I'm not sure it will work since command-line scripts expect arguments on the command line and CGI scripts expect query strings and form variables, but you might be able to re-implement the script as a non-windowing CGI...

Rick Poulin

Seems to me he's got the impersonation piece working fine. CGI's accessed directly by http://server/iw-bin/script.ipl will run as SYSTEM or whichever user happens to be running the iwwebd.

I would think that your file tests aren't working because quite simply, your users don't have access permissions to see the file/directories you're attempting to check. You should be fine if you give the appropriate set of users READ permission all the way down to the file/dir you're checking in your script.

Kevin Butcher

The problem exists in CGI tasks and external tasks. The directories I'm checking are the directories in the workarea that they are accessing. If I star the workflow using an account that has admin access to the server it works fine. Or if I actually execute the script as an administrator from command-line it works fine. It only other users. If I turn off impersonation and have external tasks run as SYSTEM it also works fine. I'm just trying to figure out a way to not have to do that.