For scheduled searches am I required to have the same auth on all servers?


With a distributed environment am I required to have the same authentication.conf and authorize.conf on search heads and indexers? I'm using both basic auth and LDAP.

I currently get errors like this ERROR UserManagerPro - Could not get info for non-existent user="<user>" and they seem to be related to scheduled searches. I'm guessing that that the knowledge bundle is getting sent from the search head with the configured search to the indexers. I do not have the same authentication.conf or authorize.conf on the indexers, is this why I am seeing this error?

And if the same config is necessary what if I wanted to prevent users besides admin from being able to log into the indexers?

0 Karma


Hi @jmccallhbo,

If you are running search head cluster then same authentication.conf and authorize.conf is require on all search heads but not on Indexers.

When search head search the data from Indexers, search head will pass necessary authentication to Indexer in knowledge bundles, so indexer does not require same authentication.conf and authorize.conf as search head.


0 Karma
Get Updates on the Splunk Community!

Happy CX Day to our Community Superheroes!

Happy 10th Birthday CX Day!What is CX Day? It’s a global celebration recognizing innovation and success in the ...

Check out This Month’s Brand new Splunk Lantern Articles

Splunk Lantern is a customer success center providing advice from Splunk experts on valuable data insights, ...

Routing Data to Different Splunk Indexes in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. The OpenTelemetry project is the second largest ...