5.5.1

Table Of Contents
REST API Permissions
When you set permissions by using the Orchestrator REST API, you must use a set of characters to define
the permissions.
You can define the permissions for an element by including a sequence of characters in the <rights> tag of
the request body of a POST request .
The characters that you can use to set permissions through the Orchestrator REST API have specific
meanings.
Table 21. Orchestrator REST API Permissions Character Set
Character Description
r
Gives view permissions.
x
Gives execute permissions.
i
Gives inspect permissions.
c
Gives edit permissions.
a
Gives administrative permissions.
Example: Syntax for Setting Permissions
You can use the following example syntax in the request body of a POST request at the URL of an
Orchestrator element's permissions.
<permissions xmlns="http://www.vmware.com/vco">
<permission>
<principal>cn=vcousers,ou=vco,dc=appliance</principal>
<rights>ric</rights>
</permission>
</permissions>
By setting ric permissions in the <rights> tag of the request body, you allow members of the vcousers user
group to view, inspect, and edit the Orchestrator element.
Retrieve the Permissions of a Workflow
You can retrieve information about the permissions of a workflow by using the Orchestrator REST API.
Procedure
1 Make a GET request and retrieve the ID of the workflow from the list of returned workflows:
GET http://{vcoHost}:{port}/vco/api/workflows/
2 Make a GET request at the URL of the workflow's permissions:
GET http://{vcoHost}:{port}/vco/api/workflows/{workflowID}/permissions/
If the GET request is successful, you receive the status code 200. Information about the workflow's
permissions is available in the response body.
Developing a Web Services Client for VMware vCenter Orchestrator
40 VMware, Inc.