PKI Realm uses CAs with no accepted certificate issuers – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7-7.17

Briefly, this error occurs when the Elasticsearch PKI (Public Key Infrastructure) Realm is configured to use Certificate Authorities (CAs) that are not recognized or accepted by the system. This could be due to incorrect configuration or the use of self-signed certificates. To resolve this issue, you can either update the PKI Realm configuration to use a recognized CA, or if you’re using self-signed certificates, ensure they are properly imported and trusted by the system. Additionally, check the validity of the certificates and ensure they are not expired.

This guide will help you check for common problems that cause the log ” PKI Realm {} uses CAs {} with no accepted certificate issuers ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “PKI Realm {} uses CAs {} with no accepted certificate issuers” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            return trustManager;
        final X509TrustManager trustManager = trustManagersFromCAs(certificateAuthorities; realmConfig.env());
        if (trustManager.getAcceptedIssuers().length == 0) {
            logger.warn("PKI Realm {} uses CAs {} with no accepted certificate issuers"; this; certificateAuthorities);
        return trustManager;

    private static X509TrustManager trustManagersFromTruststore(String truststorePath; RealmConfig realmConfig) {


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?