POST Codesign/RenameProject
Renames a CodeSign Protect project.
Requirements
- Permissions:
The caller must be a Code Signing Administrator, or a Owner.
- 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
Specify either Dn, Guid or Id.
Name |
Description |
---|---|
Dn |
(Optional) The Distinguished Name (DN) of the signing project. Use the appropriate syntax. For example, in Postman: \\VED\\Code Signing\\Projects\\[YourPrjName]. |
Guid |
(Optional)The GUID that uniquely identifies the signing project. |
Id |
(Optional)The signing project identifier. |
NewDn |
Required. The DN of the signing project. Use this syntax: "Dn": "\\VED\\Code Signing\\Projects\\[ProjectName]. |
Returns
For valid requests, RenameProject returns a HTTP 200 message and the following data in the message body:
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 a project
Request
POST https://codesign.venafi.example/vedsdk/Codesign/RenameProject Authorization:Bearer 4MyGeneratedBearerTknz== { "Dn": "\\VED\\Code Signing\\Projects\\APIProjectDraft", "NewDn": "\\VED\\Code Signing\\Projects\\Lab 4" }
Response
HTTP/1.1 200 OK { "Result": 1, "Success": true }