Skip to main content
  • EN

Hi,

In my FME Server, I published a "master" workspace with an admin user called psl. This master process basically invokes another FME workspaces through a FMEJobsubmitter.

When I run this process on the FME Server, the username is logged correctly only for the master process, but for the child process the username that is logged is psl.

How can I do that it logs the correct user for the child processes too?

Which username have you specified in the FMEServerJobSubmitter?

Which username have you specified in the FMEServerJobSubmitter?

it's psl..
it's psl..
There's your explanation :-)

 

The child job runs as the user specified in the FMEServerJobSubmitter.
There's your explanation :-)

 

The child job runs as the user specified in the FMEServerJobSubmitter.
That's not the question

 

 

If you want to retrieve the active username used to run the master workspace, you can use the FME Server Parameter "FME_SECURITY_USER" in the FMEServerJobSubmitter:

However, as far as I know there's no way to get the associated password. I suspect that is for security reasons.

Be aware that the FME_SECURITY_USER parameter is defined as an empty string when running under FME Desktop.

If you want to retrieve the active username used to run the master workspace, you can use the FME Server Parameter "FME_SECURITY_USER" in the FMEServerJobSubmitter:

However, as far as I know there's no way to get the associated password. I suspect that is for security reasons.

Be aware that the FME_SECURITY_USER parameter is defined as an empty string when running under FME Desktop.

Just to complement your answer I created another public parameter 'Password'. On the server side I enter it and it worked. Thanks

 

 

Just to complement your answer I created another public parameter 'Password'. On the server side I enter it and it worked. Thanks

 

 

Good to hear you found a solution. Just be aware that public parameters containing passwords will be visible in plain-text in the FME Server GUI / job logs, even if you define them of type password and they appear scrambled! According to Safe this is by design, the reason being that you should never send passwords as plain text if they are important to you, and I kinda agree with that.

 

So be aware that casual users might be able to stumble over someone elses password using this solution.

 

Reply


Community Stats

30,457
Posts
115,658
Replies
38,274
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.