POST Config/GuidToDn
Translates a GUID into an Object DN.
Requirements
- Permissions: The caller must have View permission to the requested object.
- Token scope: Any valid scope, such as Agent, Certificate, or SSH
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
|
Name |
Description |
|---|---|
|
ObjectGUID |
The GUID of an object to be translated. To get the GUID, call POST Config/Find. |
Returns
|
Name |
Description |
|---|---|
|
HTTP 200 |
For valid requests, this call returns a HTTP 200 message and the following data in the message body:
|
|
HTTP 400 |
For invalid requests, this call returns HTTP 400 Bad Request and the following data in the message body:
|
Example: Find DN information based on its GUID
Request
POST https://tpp.venafi.example/vedsdk/Config/GuidToDn
Authorization:Bearer 4MyGeneratedBearerTknz==
{
"ObjectGUID":"{c7fdd8d1-1fb2-4cd0-a041-9a020245a6df}"
}
Response
HTTP/1.1 200 OK
{
"ClassName":"Policy",
"HierarchicalGUID":"{19f0795c-...}{e3712316-...d}{61045a15-...}",
"ObjectDN":"\\VED\\Policy\\Certificates",
"Result":1,
"Revision":724335
}