Reviewed-by: Kacur, Michal <michal.kacur@t-systems.com> Co-authored-by: Zheng, Xiu <zhengxiu@huawei.com> Co-committed-by: Zheng, Xiu <zhengxiu@huawei.com>
7.7 KiB
Modifying Kibana Public Access Control
Function
This API is used to modify the Kibana public network access whitelist.
Debugging
You can debug this API in . Automatic authentication is supported.
URI
POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/whitelist/update
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. For details, see Obtaining a Project ID and Name. |
cluster_id |
Yes |
String |
ID of the cluster that you want to change Kibana access control |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
whiteList |
Yes |
String |
Whitelisted IP addresses or network segments that can access Kibana. Separate them with commas (,), and each IP address or network segment must be unique. |
Response Parameters
None
Request Example
The latest whitelist is displayed as follows.
{ "whiteList" : "192.168.0.21" }
Response Example
None
Status Codes
Status Code |
Description |
---|---|
200 |
The request is processed successfully. |
400 |
Invalid request. Modify the request instead of retrying. |
409 |
The request cannot be processed due to a conflict. This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request. |
412 |
The server does not meet one of the requirements that the requester puts on the request. |