Obtaining SSL Certificates
Function
Obtain SSL certificates.
URI
GET /v2/{project_id}/apic/certificates
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| project_id | Yes | String | Project ID. For details about how to obtain the project ID, see Appendix > Obtaining a Project ID in the ROMA Connect API Reference. |
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| offset | No | Long | Offset from which the query starts. If the offset is less than 0, the value is automatically converted to 0. |
| limit | No | Integer | Number of items displayed on each page. |
| name | No | String | Certificate name. |
| common_name | No | String | Certificate domain name. |
| signature_algorithm | No | String | Certificate signature algorithm |
| type | No | String | Certificate scope. |
| instance_id | Yes | String | ID of the certificate instance. |
| algorithm_type | No | String | Certificate algorithm type:
|
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| X-Auth-Token | Yes | String | User token, which can be obtained by calling the IAM API (value of X-Subject-Token in the response header). |
Response Parameters
Status code: 200
| Parameter | Type | Description |
|---|---|---|
| size | Integer | Length of the returned resource list. |
| total | Long | Number of resources that match the query conditions. |
| certs | Array of CertBase objects | Certificate content. |
| Parameter | Type | Description |
|---|---|---|
| id | String | Certificate ID. |
| name | String | Certificate name. |
| type | String | Certificate type. Options:
|
| instance_id | String | Instance ID.
|
| project_id | String | Project ID. |
| common_name | String | Domain name. |
| san | Array of strings | SAN. |
| not_after | String | Validity period end time. |
| signature_algorithm | String | Signature algorithm. |
| create_time | String | Creation time. |
| update_time | String | Update time. |
| algorithm_type | String | Certificate algorithm type:
|
| is_has_trusted_root_ca | Boolean | Whether a trusted root certificate (CA) exists. The value is true if trusted_root_ca exists in the bound certificate. |
Status code: 400
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code. |
| error_msg | String | Error description. |
Status code: 401
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code. |
| error_msg | String | Error description. |
Status code: 403
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code. |
| error_msg | String | Error description. |
Status code: 500
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code. |
| error_msg | String | Error description. |
Example Requests
None
Example Responses
Status code: 200
OK
{
"total" : 1,
"size" : 1,
"certs" : [ {
"id" : "a27be832f2e9441c8127fe48e3b5ac67",
"name" : "cert_demo",
"type" : "instance",
"project_id" : "73d69ae0cfcf460190522d06b60f05ad",
"instance_id" : "f0fa1789-3b76-433b-a787-9892951c620e",
"common_name" : "apigtest.xxx.com",
"san" : [ "apigtest.xxx.com", "*.san.com" ],
"not_after" : "2021-04-26T09:03:30Z",
"signature_algorithm" : "SHA256-RSA",
"create_time" : "2021-08-26T07:27:06.304004Z",
"update_time" : "2021-08-26T07:27:06.304004Z",
"algorithm_type" : "RSA"
} ]
} Status code: 400
Bad Request
{
"error_code" : "APIG.2012",
"error_msg" : "Invalid parameter value,parameterName:dict_name. Please refer to the support documentation"
} Status code: 401
Unauthorized
{
"error_code" : "APIG.1002",
"error_msg" : "Incorrect token or token resolution failed"
} Status code: 403
Forbidden
{
"error_code" : "APIG.1005",
"error_msg" : "No permissions to request this method"
} Status code: 500
Internal Server Error
{
"error_code" : "APIG.9999",
"error_msg" : "System error"
} Status Codes
| Status Code | Description |
|---|---|
| 200 | OK |
| 400 | Bad Request |
| 401 | Unauthorized |
| 403 | Forbidden |
| 500 | Internal Server Error |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.