POST Config/ReadDn
Returns values of an object Distinguished Name (DN) based. You can only use a DistinguishedName attribute from the schema. The response does not include policy-assigned values.
Requirements
- Permissions: The caller must have Read permission to the requested object.
- Token scope: Configuration
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 |
---|---|
ObjectDN |
The Distinguished Name (DN) of the object. |
AttributeName |
A value, from the BaseSchema.xml. Use a value that is:
|
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: What consumes my certificate?
Request
POST https://tpp.venafi.example/vedsdk/Config/ReadDn Authorization:Bearer 4MyGeneratedBearerTknz== { "ObjectDN":"\\VED\\Policy\\folder\\Certificate", "AttributeName":"Consumers" }
Response
HTTP/1.1 200 OK { "Result":1, "Values":[ "\\VED\\Policy\\folder\\Device2\\Basic1", "\\VED\\Policy\\folder\\Device2\\Basic3" ] }