POST Config/AddDnValue
Adds an extra attribute value to an Object Distinguished Name (DN).
CAUTION If you apply additional values to attributes that only allow one attribute value, unexpected results may occur. To determine whether an attribute can have multiple values, search for the class attribute in the Web SDK Object class reference. To confirm existing attribute settings, call POST Config/ReadDn.
To associate a certificate to an Application object or vice versa, call POST Certificates/Associate instead. Classes that have attributes that allow multiple values:
- Discovery object
- F5 Authentication Bundle Application object
- Group object
- Parent class—Application Base
- Parent class—Credential Base
- Parent class—Schedule Base
- Parent class—Top
- Parent class—X509 Certificate Base
- Person object
- Workflow Ticket object
Requirements
- Permissions: The caller must have Write permission to the requested object.
- 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
Name |
Description |
---|---|
ObjectDN |
The Distinguished Name (DN) of the object. |
AttributeName |
The name of an attribute that allows multiple values. For more information, see How to find class names and attributes. |
Value |
The value to add to the attribute. |
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 1: Add another Exclusion to a Network Discovery job
Request for Example 1
POST https://tpp.venafi.example/vedsdk/Config/AddDnValue
Authorization:Bearer 4MyGeneratedBearerTknz==
{ "ObjectDN":"\\VED\\Discovery\\My Network Discovery Job", "AttributeName":"Discovery Exclusion DN", "Value":"\\VED\\Discovery\\Sensitive Address Exclusion" }
Response for Example 1
HTTP/1.1 200 OK
{
"Result": 1
}
Example 2: Add another Target Channel to Notification Rule
Request for Example 2
POST https://tpp.venafi.example/vedsdk/Config/AddDnValue
Authorization:Bearer 4MyGeneratedBearerTknz==
{ "ObjectDN":"\\VED\\Logging\\Notification Rules\\My Notification Rule", "AttributeName":"Log Channel", "Value":"\\VED\\Logging\\Channels\\Email to Network Operations" }
Response for Example 2
HTTP/1.1 200 OK
{
"Result": 1
}