ACTIVATE_UC_OBJECT running jobs on unrelated agents

Discussion created by DanielGates628573 on Dec 21, 2017
Latest reply on Dec 21, 2017 by Antoine_Sauteron_1266

Not sure this is by design but just notice the following behavior.

I have a client that can run jobs against agents AGENT1 and AGENT2
There is also another agent AGENT3 that is not associated with this client

If I create a job (runjob) and hard code the agent as AGENT3, as expected it returns an access denied error.

If I then create another job (calljob) with a variable &DUMMYAGENT# set to "AGENT3" and set the agent to &DUMMYAGENT#  in runjob, when I use ACTIVATE_UC_OBJECT to call runjob from calljob, runjob seems to be able to execute against AGENT3?

Does this sound right?