I know that the run_as user generally defaults to the creator_user, but I would like to find the defined run_as user for each of our jobs. Unfortunately, I'm unable to locate that field in the api.
thanks, I picked my own reply as the 'right' answer. i'd still recommend that the jobs api perhaps incorporate run-as-user in the 'list' method, rather than only in job details.
>> Thanks for reaching out to us. In order to update run_as_user in API 2.1, you need to change the job owner to the respective user defined in the access_control_list.Thank you. Unfortunately, I am not trying to update the run_as_user, but I am try...
