Ignoring setting because the IdP metadata is being loaded from a file – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Ignoring setting because the IdP metadata is being loaded from a file ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-file, metadata and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Ignoring setting [{}] because the IdP metadata is being loaded from a file” classname is SamlRealm.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         final String entityId = require(config; IDP_ENTITY_ID);
        final Path path = config.env().configFile().resolve(metadataPath);
        final FilesystemMetadataResolver resolver = new FilesystemMetadataResolver(path.toFile());

        if (IDP_METADATA_HTTP_REFRESH.exists(config.settings())) {
            logger.info("Ignoring setting [{}] because the IdP metadata is being loaded from a file";
                    RealmSettings.getFullSettingKey(config; IDP_METADATA_HTTP_REFRESH));
        }

        // We don't want to rely on the internal OpenSAML refresh timer; but we can't turn it off; so just set it to run once a day.
        // 
TODO : Submit a patch to OpenSAML to optionally disable the timer



 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content