Could not encrypt access token and refresh token string – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.2-8.9

Briefly, this error occurs when Elasticsearch fails to encrypt the access token and refresh token string due to issues with the encryption key or the encryption process itself. This could be due to an incorrect or missing encryption key, or a problem with the encryption algorithm. To resolve this issue, you can try regenerating the encryption key, ensuring it is correctly configured in Elasticsearch. If the problem persists, check the encryption algorithm being used and ensure it is compatible with Elasticsearch. Also, ensure that the tokens are correctly formatted and not corrupted.

This guide will help you check for common problems that cause the log ” could not encrypt access token and refresh token string ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, refresh.

Log Context

Log “could not encrypt access token and refresh token string” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    updateMap.put("superseding.encrypted_tokens"; encryptedAccessAndRefreshToken);
                    updateMap.put("superseding.encryption_iv"; Base64.getEncoder().encodeToString(iv));
                    updateMap.put("superseding.encryption_salt"; Base64.getEncoder().encodeToString(salt));
                } catch (GeneralSecurityException e) {
                    logger.warn("could not encrypt access token and refresh token string"; e);
                    onFailure.accept(invalidGrantException("could not refresh the requested token"));
            assert seqNo != SequenceNumbers.UNASSIGNED_SEQ_NO : "expected an assigned sequence number";
            assert primaryTerm != SequenceNumbers.UNASSIGNED_PRIMARY_TERM : "expected an assigned primary term";