I have a scenario whereby I need the Jamf Pro server to execute some action, and pass on this information to the client.
It should work like this -
client is triggered to install 'policy A' --> client asks Jamf Pro server for infromation X (which is needed by the client to complete the policy installation) --> Jamf Pro executes some script/API call to a separate internally-hosted webservice --> Jamf Pro recevies the output from the webservice and passes it to the client
The webservice is not publicly accessible, thus the client is unable to reach it, and has to rely on the Jamf Pro server to make the API call on its behalf.
Is this somehow possible?
