topic Re: AuthenticationManagerLDAP Error Message and BaseDN setting in Security

AuthenticationManagerLDAP Error Message and BaseDN setting

asarolkar — Thu, 28 Feb 2013 00:37:43 GMT

Hi All,

We are currently getting the following error

ERROR AuthenticationManagerLDAP - Could not find user="nobody" with strategy="LDAP DC02"
host=something

Not sure what error is causing this error.

Is it a known error message that appears when Splunk does not successfully bind to AD?
Is it a LDAP-role mapping issue ?
Should I perhaps be looking at BaseDN/groupbaseDN configuration ?

The user "nobody" looks a bit suspicious.

Re: AuthenticationManagerLDAP Error Message and BaseDN setting

gadjet — Sat, 03 Aug 2013 11:02:12 GMT

The user 'nobody' is supposed to be for 'configuration items' that aren't assigned a user.

I'm experiencing the same errors, and I would also like to know why it occurs, and how to stop it.

Re: AuthenticationManagerLDAP Error Message and BaseDN setting

xzjc3q — Fri, 07 Mar 2014 16:11:03 GMT

I have the same issue as well. Would be interested in an answer.

Re: AuthenticationManagerLDAP Error Message and BaseDN setting

lmyrefelt — Tue, 17 Jun 2014 09:41:08 GMT

No
No, not really
No

I found dshpritz answer here helpfull;
http://answers.splunk.com/answers/49525/splunkdlog-error-message

Running; find /path/to/splunk/apps -iname *.meta -exec grep -il "nobody" {} \; gives me all objects owned by nobody and thus i can easily change it to an more appropriate context / user .

Hope it helps 🙂

Re: AuthenticationManagerLDAP Error Message and BaseDN setting

lmyrefelt — Tue, 17 Jun 2014 09:41:50 GMT

1.No
2. No, not really
3. No

I found dshpritz answer here helpfull;
http://answers.splunk.com/answers/49525/splunkdlog-error-message
Running; find /path/to/splunk/apps -iname *.meta -exec grep -il "nobody" {} ; gives me all objects owned by nobody and thus i can easily change it to an more appropriate context / user .
Hope it helps 🙂

Re: AuthenticationManagerLDAP Error Message and BaseDN setting

NageswariV — Mon, 22 Sep 2014 17:18:11 GMT

HI, I find the same error with some of my users as well. how to resolve this issue? please help.