POST Codesign/RenameApplication
Renames a signing application entry in CodeSign Protect. The actual signing tool name remains unchanged.
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 application. Use the appropriate syntax. For example, in Postman: \\VED\\Code Signing\\Signing Applications\\[YourSgnApp]. To get this value, call POST Codesign/EnumerateApplications. |
NewDn |
The new DN to identify the signing application. |
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 only the DN of a signing tool
Request
POST https://codesign.venafi.example/vedsdk/Codesign/RenameApplication Authorization:Bearer 4MyGeneratedBearerTknz== { "Dn":"\\VED\\Code Signing\\Signing Applications\\MySigningApplication", "NewDn":"\\VED\\Code Signing\\Signing Applications\\SigningToolFor Lab4" }
Response
HTTP/1.1 200 OK { "Result":1, "Success":true }