POST Codesign/RenameApplicationCollection
Renames a signing Application collection.
Requirements
- Permissions:
The caller must be a Code Signing Administrator or application administrator.
- Token scope: Codesign: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 |
---|---|
Dn |
The Distinguished Name (DN) of the signing collection. Use the appropriate syntax. For example, in Postman: \\VED\\Code Signing\\Signing Applications\\[YourSgnAppCollection]. To get this value, call POST Codesign/EnumerateApplicationCollections. |
NewDn |
The new DN to identify the set of signing tools. |
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: Rename an application collection
Request
POST https://codesign.venafi.example/vedsdk/Codesign/RenameApplicationCollection Authorization:Bearer 4MyGeneratedBearerTknz== { "Dn": "\\VED\\Code Signing\\Signing Applications\\MyCollection", "NewDn": "\\VED\\Code Signing\\Signing Applications\\MySigningToolset" }
Response
HTTP/1.1 200 OK { "Result": 1, "Success": true }