Allowing a Talend Data Preparation or Talend Data Stewardship user to interact with Remote Engine Gen2 allocated to a workspace

You must assign the Execute permission to the user on the appropriate workspace.

1. Use the GET /orchestration/workspaces endpoint to retrieve the ID of the workspace you are setting the permissions for.
   You can narrow the search to a single environment by using the query=environment.name=={environmentName} query parameter.

   Example

   GET https://api.us.cloud.talend.com/orchestration/workspaces?query=environment.name==default

2. Use the GET /account/users endpoint to retrieve the ID of the user you want to set the permissions for.

   Example

   GET https://api.us.cloud.talend.com/account/users?page=1&size=50

3. Use the POST /security/workspaces/{workspaceId}/users/{userId}/permissions endpoint and add the Execute permission in body of the request.

   Example

   POST https://api.us.cloud.talend.com/security/workspaces/7a35e78eaea645620e47f826/users/d13404b5-e9nc-4g5f-9904-a5f0dc287fb0/permissions
   ["EXECUTE"]

   Information noteNote: When a user account has the TMC_ENGINE_USE user permission, this account can be granted the EXECUTE and the VIEW workspace permissions only. This combination allows users that do not have the Operator role to use Remote Engines to run tasks without having to consume a seat.
4. Use the GET /security/workspaces/{workspaceId}/users/{userId}/permissions endpoint to validate the update.

   Example

   GET https://api.us.cloud.talend.com/security/workspaces/7a35e78eaea645620e47f826/users/d13404b5-e9nc-4g5f-9904-a5f0dc287fb0/permissions

   The response body should contain the workspace ID, and all assigned permissions.

   "workspaceId": "7a35e78eaea645620e47f826",
   "userId": "d13404b5-e9nc-4g5f-9904-a5f0dc287fb0",
   "permissions":["EXECUTE"]