DisassociateAdditionalCertificatesWithListener - Server Load Balancer

Disassociates additional certificates from a listener that uses SSL over TCP.

Operation description

DisassociateAdditionalCertificatesWithListener is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListListenerCertificates operation to query the status of the task:

If an additional certificate is in the Dissociating state, the additional certificate is being disassociated.
If an additional certificate is in the Dissociated state, the additional certificate is disassociated.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

Parameter	Type	Required	Description	Example
AdditionalCertificateIds	array	Yes	The additional certificates. You can disassociate up to 15 additional certificates from a listener in each request.
	string	Yes	The additional certificates. Only server certificates are supported. You can disassociate up to 15 additional certificates from a listener in each request.	12315790343_166f8204689_1714763408_70998****
ListenerId	string	Yes	The listener ID. You must specify the ID of a listener that uses SSL over TCP.	lsr-bp1bpn0kn908w4nbw****
DryRun	boolean	No	Specifies whether to perform a dry run, without performing the actual request. Valid values: true: performs only a dry run. The system checks the request for potential issues, including missing parameter values, incorrect request syntax, and service limits. If the request fails the dry run, an error message is returned. If the request passes the dry run, the `DryRunOperation` error code is returned. false(default): performs a dry run and performs the actual request. If the request passes the dry run, a 2xx HTTP status code is returned and the operation is performed.	true
ClientToken	string	No	The client token that is used to ensure the idempotence of the request. You can use the client to generate the token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters. Note If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.	123e4567-e89b-12d3-a456-426655440000
RegionId	string	No	The region ID of the Network Load Balancer (NLB) instance. You can call the DescribeRegions operation to query the most recent region list.	cn-hangzhou

Response parameters

Parameter	Type	Description	Example
	object	RpcResponse
RequestId	string	The request ID.	365F4154-92F6-4AE4-92F8-7FF34B540710
JobId	string	The ID of the asynchronous task.	72dcd26b-f12d-4c27-b3af-18f6aed5****

Examples

Sample success responses

JSONformat

{
  "RequestId": "365F4154-92F6-4AE4-92F8-7FF34B540710",
  "JobId": "72dcd26b-f12d-4c27-b3af-18f6aed5****"
}

Error codes

HTTP status code	Error code	Error message
400	IncorrectStatus.listener	The status of %s [%s] is incorrect.
400	IncorrectStatus.certificate	The status of %s [%s] is incorrect.
400	IncorrectStatus.loadbalancer	The status of %s [%s] is incorrect.
400	OperationDenied.Protocol	The operation is not allowed because of %s.
400	OperationDenied.DefaultCertificateUsed	The operation is not allowed because of %s.
400	ResourceNotAssociated.Certificate	The specified resource %s is not associated.
400	OperationDenied.CaCertificateUsed	The operation is not allowed because of %s.
404	ResourceNotFound.listener	The specified resource %s is not found.
404	ResourceNotFound.loadbalancer	The specified resource %s is not found.

For a list of error codes, visit the Service error codes.

Change history

Change time

Summary of changes

Operation

2023-12-18

The Error code has changed

see changesets

Change item	Change content
Error Codes	The Error code has changed.
	Error Codes 400 change
	Error Codes 404 change