Issuer CA Create - Microsoft Standalone CA
Payload
| Name | Description |
|---|---|
| kubeCaSettingName
|
Unique name to identify the KUBE CA setting configuration. |
| clusterPolicy
|
Cluster policy to which the cluster is associated to |
| caAccount
|
Account associated with the CA. |
| certificateProfile
|
Type of certificate. Possible Values: Server, Client |
| validityUnit
|
Validity of the certificate. Possible Values: Days, Months, Years |
| casetting_type
|
Type of the CA setting type. Possible Values: CA Setting, CA Setting Cluster |
| groupName
|
Name of group where certificate might be pushed to after creation. |
| certificateAuthority
|
Name of the Certificate Authority being
configured. Possible Values: Microsoft Standalone |
Response Structure
- Status Code: 200 OK
- Message: Successful
- Headers:
- Content-Type: application/json
| Name | Description |
|---|---|
| response
|
Issuer CA created successfully |
| message
|
Success message or failure description in case of error. |
| appStatusCode
|
Application specific status code for the response. Will be non-null for failure response. |
| tags | More info in case of failure response. |
Sample Request/Response
https://<IP/HostName/TenantName>:<GWPORT>/avxapi/execute-hook?gwsource=external
POST Content type: application/json Username: <> Password: <>
{
"payload": {
"hook": {
"name": "Kube CA Settings"
},
"input": {
"action": "add",
"payload": {
"kubeCaSettingName": "aaqdsdcweq",
"clusterPolicy": "cluster_polisy-ms-standalone_ca_caset_clu",
"caAccount": "Microsoft_Standalone_Crypto_Mesh_CA",
"certificateProfile": "Server",
"casetting_type": "CA Setting",
"groupName": "CryptoMesh_MS_Standalone_Group",
"certificateAuthority": "Microsoft Standalone"
}
}
}
}{
"response": {
"status": "Success",
"output": {
"status": "Success",
"response": "Issuer CA created successfully"
},
"type": "script"
},
"message": null,
"appStatusCode": null,
"tags": null,
"headers": null
}Reference
- 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.