Realm is in user-search mode – base dn= search filter= – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is trying to authenticate a user using LDAP or Active Directory, but it’s having trouble finding the user’s DN (Distinguished Name). This could be due to incorrect configuration of the user search filter or base DN. To resolve this issue, you can: 1) Verify the correctness of the base DN and user search filter in your realm configuration. 2) Check the connectivity and accessibility of your LDAP/AD server. 3) Ensure that the user exists in the LDAP/AD server and that Elasticsearch has the necessary permissions to search for users.

This log is related to search problems, in addition to reading the guide below you can use the free Search Log Analyzer. With Opster’s Analyzer, you can easily locate slow searches and understand what led to them adding additional load to your system. The tool is free and takes just 2 minutes to run.

Log Context

Log “Realm [{}] is in user-search mode – base_dn=[{}]; search filter=[{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                "[" + RealmSettings.getFullSettingKey(config; LdapUserSearchSessionFactorySettings.SEARCH_BASE_DN) + "] must be specified"
        scope = config.getSetting(LdapUserSearchSessionFactorySettings.SEARCH_SCOPE);
        searchFilter = getSearchFilter(config);"Realm [{}] is in user-search mode - base_dn=[{}]; search filter=[{}]";; userSearchBaseDn; searchFilter);

    static List extends Setting.AffixSetting>> configuredUserSearchSettings(RealmConfig config) {
        return Stream.of(


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?