Delete CA
Before you begin
- Refer to Prerequisites in the PKI User Guide.
Request Structure
| Endpoint: | v1/pki/ca/delete/<CAName> |
| Type: | DELETE |
| Sample URL: |
|
| Headers | |
| Content-Type: | application/json |
| Name | Description |
|---|---|
| sessionId
|
(Mandatory) Session Id received after
login. Type: String Constraint: Required if username and password are not provided. |
| username
|
(Mandatory) AppViewX login username. Type: String Constraint: Required if sessionId is not provided. |
| password
|
(Mandatory) AppViewX login password. Type: String Constraint: Required if sessionId is not provided. |
Response Structure
Response returns string of type application/json with the following body parameters:
| Name | Description |
|---|---|
| response | Indicates status of the API operation. |
| message | Success message - PKIaaS approval request initiated
successfully. Type: String |
| appStatusCode | Application specific status code for the response. It is a
non-null value for a failure response. Type: String |
| tags | Additional information in case of failure response. |
Status Codes
| HTTP Code | appStatusCode | Response Message |
|---|---|---|
| 200 Accepted | null | Delete CA action has been triggered successfully. |
| 401 Unauthorized | AVX_GW_003 | Authentication failed, reason - Invalid Credentials.
Remediation: Ensure that valid username and password or a valid sessionId is provided as header parameters. |
| 400 Bad Request | DELETE_SUB_CA_FIRST | Occurs when trying to delete Root CA when Sub CA is
present. Remediation: Ensure that sub CA is deleted. |
| 400 Bad Request | INVALID_OPERATION_APPROVAL_IN_PROGRESS | Requested operation not allowed. Approval process in
progress. Remediation: Ensure that approval request is either approved, rejected, or aborted and try again. |
| 417 Expectation Failed | ACCESS_NOT_PRESENT_TO_WRITE | When user does not have resource access to
CA. Remediation: Ensure that valid |
Sample Response
{
"response": "Success",
"message": "PKIaaS approval request initiated successfully.",
"appStatusCode": null,
"tags": {},
"headers": null
}References
- IP/HostName/TenantName: Replace with the actual IP address, hostname,
or tenant name based on the specific configuration in AppViewX.
- IP: A unique identifier assigned to each device connected to
a computer network that uses the Internet Protocol for communication
The IP address will be included in the endpoint URL for an on-prem deployment.
- HostName: A human-readable label assigned to a device (host)
on a network
The hostname will be included in the endpoint URL for an on-prem deployment.
- TenantName: An identifier label for a tenant given to
indicate which tenant's data the API request will
access/modify
The tenant name will be included in the endpoint URL for a SaaS deployment.
- IP: A unique identifier assigned to each device connected to
a computer network that uses the Internet Protocol for communication
- GWPORT: AppViewX gateway port
A gateway port refers to a network port through which data is sent and received to communicate with a gateway in an on-prem deployment.
Example: 31443
- avxapi: Path parameter value (static) that is part of the endpoint's URL
- Endpoint: Endpoint of the API, for example: execute-hook
- gwsource: Source or origin of a gateway, for example: external.