Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Feature
- Users want to run a job e.g. in a Unix environment for a specific user account, see link to SourceForge.
- This can be achieved e.g. by using:
sudo su - <account>
- Please note that sudoers must be configured to use su - without password.
- This can be achieved e.g. by using:
- The user account for the task run should be used from the user account in JOC Cockpit who caused the task start.
Implementation
- The JOC Cockpit REST Web Service should automatically create an order/task parameter SCHEDULER_JOC_USER_ACCOUNT with the value of the JOC Cockpit user account who caused the order/task start.
- If an order/task start is performed by the web service then an existing parameter with the same name will be overwritten .
- If an order/task start is performed without web service interaction then this parameter will not be set. Should this parameter exist from the order/task then it will not be modified.
- For Unix environments this should allow to configure shell jobs e.g. like this:
sudo su - $SCHEDULER_PARAM_SCHEDULER_JOC_USER_ACCOUNT
- For Windows environments see
JS-1771
Attachments
Issue Links
- requires
-
JS-1771 Master should substitute task/order parameters for a jobs credentials key
- Released
- links to