Clear Service Account Token Cache APIedit

Clear Service Account Token Cache Requestedit

A ClearServiceAccountTokenCacheRequest supports clearing service account token cache for the given namespace, service name and token names. It can also clear the entire cache if a * is specified for the token name.

ClearServiceAccountTokenCacheRequest request = new ClearServiceAccountTokenCacheRequest(
    "elastic", 
    "fleet-server", 
    "token1" 
);

Namespace of the service account

Service name of the service account

Name(s) for the service account token to be evicted from the cache

Synchronous executionedit

When executing a ClearServiceAccountTokenCacheRequest in the following manner, the client waits for the ClearSecurityCacheResponse to be returned before continuing with code execution:

ClearSecurityCacheResponse response = client.security().clearServiceAccountTokenCache(request, RequestOptions.DEFAULT);

Synchronous calls may throw an IOException in case of either failing to parse the REST response in the high-level REST client, the request times out or similar cases where there is no response coming back from the server.

In cases where the server returns a 4xx or 5xx error code, the high-level client tries to parse the response body error details instead and then throws a generic ElasticsearchException and adds the original ResponseException as a suppressed exception to it.

Asynchronous executionedit

Executing a ClearServiceAccountTokenCacheRequest can also be done in an asynchronous fashion so that the client can return directly. Users need to specify how the response or potential failures will be handled by passing the request and a listener to the asynchronous clear-service-account-token-cache method:

client.security().clearServiceAccountTokenCacheAsync(request, RequestOptions.DEFAULT, listener); 

The ClearServiceAccountTokenCacheRequest to execute and the ActionListener to use when the execution completes

The asynchronous method does not block and returns immediately. Once it is completed the ActionListener is called back using the onResponse method if the execution successfully completed or using the onFailure method if it failed. Failure scenarios and expected exceptions are the same as in the synchronous execution case.

A typical listener for clear-service-account-token-cache looks like:

ActionListener<ClearSecurityCacheResponse> listener = new ActionListener<ClearSecurityCacheResponse>() {
    @Override
    public void onResponse(ClearSecurityCacheResponse clearSecurityCacheResponse) {
        
    }

    @Override
    public void onFailure(Exception e) {
        
    }
};

Called when the execution is successfully completed.

Called when the whole ClearServiceAccountTokenCacheRequest fails.

Clear Service Account Token Cache Responseedit

The returned ClearSecurityCacheResponse allows to retrieve information about where the cache was cleared.

List<ClearSecurityCacheResponse.Node> nodes = response.getNodes(); 

the list of nodes that the cache was cleared on