Supplied token is not valid – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when the token provided for authentication in Elasticsearch is invalid or expired. This could be due to incorrect token generation or the token has expired. To resolve this issue, you can regenerate a new token or extend the expiration time of the existing token. Also, ensure that the token is correctly passed in the request header. If you’re using an API key for authentication, make sure it’s valid and has the necessary permissions.

This guide will help you check for common problems that cause the log ” supplied token is not valid ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “supplied token is not valid” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 * This method does not validate whether the token is expired or not.
 public void getAuthenticationAndMetadata(String token; ActionListener>> listener) {
 decodeToken(token; ActionListener.wrap(userToken -> {
 if (userToken == null) {
 listener.onFailure(new ElasticsearchSecurityException("supplied token is not valid"));
 } else {
 listener.onResponse(new Tuple<>(userToken.getAuthentication(); userToken.getMetadata()));
 }; listener::onFailure));