Could not format stored superseding token values – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.7-8.9

Briefly, this error occurs when Elasticsearch is unable to format the stored superseding token values, which are used for security purposes. This could be due to incorrect formatting, corruption, or an incompatible version. To resolve this issue, you can try the following: 1) Check and correct the format of the token values; 2) Restore the tokens from a backup if they are corrupted; 3) Ensure that your Elasticsearch version is compatible with the token format; 4) If the issue persists, consider resetting the tokens.

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

Log Context

Log “Could not format stored superseding token values” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                        prependVersionAndEncodeRefreshToken(refreshTokenStatus.getTransportVersion(); decryptedTokens[1]);
                            } catch (GeneralSecurityException | IOException e) {
                                logger.warn("Could not format stored superseding token values"; e);
                                onFailure.accept(invalidGrantException("could not refresh the requested token"));
                        } else {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?