Modifying Kibana Public Access Control
Function
This API is used to modify the Kibana access permission by modifying the Kibana whitelist.
URI
POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/whitelist/update
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name. |
cluster_id |
Yes |
String |
ID of the cluster whose Kibana access permission you want to modify. |
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
Example Requests
The latest whitelist
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/5c77b71c-5b35-4f50-8984-76387e42451a/publickibana/whitelist/update { "whiteList" : "192.168.0.21" }
Example Responses
None
Status Codes
Status Code |
Description |
---|---|
200 |
Request succeeded. |
400 |
Invalid request. Modify the request before retry. |
409 |
The request could not be completed due to a conflict with the current state of the resource. The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict. |
412 |
The server did not meet one of the preconditions contained in the request. |
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.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot