PUT ProcessingEngines/Folder/{folder guid}

Assigns zero or more a Platforms engines to manage certificate processing for a Policy folder. The caller must have Manage Policy permission to the Policy folder.

Requirements

  • Permissions:  The caller must also have View permission on each Platforms engine.
  • Token scope:  Configuration:Manage

Headers

  • Content type: Content-Type:application/json.

  • Token: The bearer access token that you received. For example, Authorization:Bearer 4MyGeneratedBearerTknz==. For more information, see Passing a bearer token in your API calls.

Parameters

Input parameters

Name

Description

EngineGuids

Specify this parameter as part of the JSON body. An array of Platforms engine GUIDs. In the Platforms tree, use the Venafi Platform value that appears on the Support Attributes tab. Enclose the GUID in curly braces. For example, {c4152110-1ec9-4f62-99fe-869d66264c34}

Platforms Engine Guid

{folder guid}

Specify this parameter as part of the URL. A GUID that uniquely identifies a Policy folder. Depending on your environment, the GUID may be expressed with or without curly braces {}. For example, {3d6b61d-1c71-4603-883f-25b8c2ceecdd}. In the Policy tree, use the Policy value that appears on the Support tab.

Processing Engine Folder Guid

Returns

Response description

Name

Description

HTTP 200

For valid requests, PUT ProcessingEngines/Folder/{folder guid} returns a HTTP 200 message and an empty message body.

HTTP 204

Returns NoContent when the policy folder has no processing engine assignments.

HTTP 400

Returns Bad Request for the following reasons:

  • Missing request parameter: [EngineGuids].

  • Missing resource id: [FolderGuid].
  • Number of engines should be less than 1000.

Example: Assign two Platforms engines to manage a Policy folder

Request

PUT https://tpp.venafi.example/vedsdk/ProcessingEngines/Folder/{067e26e2-5536-4a6d-915b-fbf28496125c}
Authorization:Bearer 4MyGeneratedBearerTknz==
{
   "EngineGuids":[
      "{c4152110-1ec9-4f62-99fe-869d66264c34}",
      "{153d0c3d-f9ff-4682-b801-687c7c4db0e9}"
   ]
}

Response

HTTP/1.1 200 OK
{

}