Log Authentication of elastic was terminated by realm reserved – How To Solve Related Issues



Log Authentication of elastic was terminated by realm reserved – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

This guide will help you check for common problems that cause the log ” Authentication of [elastic] was terminated by realm [reserved] ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

Log Context

Log “Authentication of [{}] was terminated by realm [{}] – {}” classname is AuthenticationService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                 userListener.onResponse(result.getUser());
                            } else {
                                // the user was not authenticated; call this so we can audit the correct event
                                request.realmAuthenticationFailed(authenticationToken; realm.name());
                                if (result.getStatus() == AuthenticationResult.Status.TERMINATE) {
                                    logger.info("Authentication of [{}] was terminated by realm [{}] - {}";
                                            authenticationToken.principal(); realm.name(); result.getMessage());
                                    Exception e = (result.getException() != null) ? result.getException()
                                            : Exceptions.authenticationError(result.getMessage());
                                    userListener.onFailure(e);
                                } else {




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Authentication Of Elastic Was Termi

2 Upgrade From 6 2 To 6 4 Gives Authe

Optimize Elasticsearch Performance

Try The Tool