Briefly, this error occurs when there’s a mismatch between the authentication method used during the creation of the refresh token and the current authentication method. This could be due to changes in the authentication settings or credentials. To resolve this, you can try the following: 1) Ensure that the same authentication method is used consistently. 2) Check if any changes have been made to the authentication settings or credentials. 3) Reissue the refresh token using the current authentication method.
This guide will help you check for common problems that cause the log ” [{}] created the refresh token while authenticated by [{}] but is now authenticated by [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, refresh.
Log Context
Log “[{}] created the refresh token while authenticated by [{}] but is now authenticated by [{}]” classname is TokenService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (clientAuthentication.getUser().principal().equals(refreshToken.getAssociatedUser()) == false) {
logger.warn("Token was originally created by [{}] but [{}] attempted to refresh it"; refreshToken.getAssociatedUser();
clientAuthentication.getUser().principal());
return Optional.of(invalidGrantException("tokens must be refreshed by the creating client"));
} else if (clientAuthentication.getAuthenticatedBy().getName().equals(refreshToken.getAssociatedRealm()) == false) {
logger.warn("[{}] created the refresh token while authenticated by [{}] but is now authenticated by [{}]";
refreshToken.getAssociatedUser(); refreshToken.getAssociatedRealm();
clientAuthentication.getAuthenticatedBy().getName());
return Optional.of(invalidGrantException("tokens must be refreshed by the creating client"));
} else {
return Optional.empty();
