Unjoin CPA

Unjoin CPA

Note: At the successful completion of the unjoin operation the current pod will become a non-federated pod that is no longer a member of the Pod Federation. All Pod Federation topology data will be removed from the current pod. GlobalEntitlement reference to this pod will be updated with an unjoin. Unjoin operation can only be performed if the current pod is not the only/last member of a Pod Federation; an uninitialize operation should be performed instead. The pod on which the operation is performed on must not have replica Connection Servers in transitional states. A Task Id is returned and can be used to track the progress and status of the unjoin operation. All the listed privileges are required -

Privileges Description
FEDERATED_LDAP_MANAGE Caller should have permission to this privilege, to perform this operation.
Request
URI
POST
https://{api_host}//localhost/rest/federation/v1/cpa/action/unjoin
COPY
Authentication
This operation uses the following authentication methods.
Responses
200

OK

Returns CPATaskResponseInfo of type(s) */*
{
    "task_id": "0103796c-102b-4ed3-953f-3dfe3d23e0fe"
}
string
task_id
Optional

Unique ID representing the task.


400

Bad Request

Operation doesn't return any data structure

401

User is not authenticated

Operation doesn't return any data structure

403

Access to the resource is forbidden

Operation doesn't return any data structure

409

Conflict | CPA not initialized for the pod | An active Pod Federation operation is detected

Operation doesn't return any data structure