Was able to add LDAP server exactly as we have it setup in Netflow Analyzer (what I assume this feature was borrowed from) but logins are showing "success" but not allowing LDAP users in.
Ideas on where to look?
2015r2.0 LDAP woes
2015r2.0 LDAP woes
You do not have the required permissions to view the files attached to this post.
Andrew J. - Do you even grok?
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: 2015r2.0 LDAP woes
I am getting the same behaviour as you, I did this on a freshly deployed VM.
Successfully added AD servers and imported users.
Trying to login just gives me Success.
We probably won't get a response from the USA techs until tomorrow.
Successfully added AD servers and imported users.
Trying to login just gives me Success.
We probably won't get a response from the USA techs until tomorrow.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: 2015r2.0 LDAP woes
I've let the techs know and tomorrow they will come back to us with what to do next. If a bug report needs to be filed they will do it.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: 2015r2.0 LDAP woes
One other question, my tests were against a Windows Domain. Is your setup a Windows Domain or a non-Windows LDAP instance?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: 2015r2.0 LDAP woes
So the problem is when importing users it's missing a variable that is normally set when editing a user. In order to fix this for the time being if you edit the users you imported, make sure they are set to AD, the AD server you selected, and have the proper AD username in the username section and save the user you should be able to use it.
Working on a fix for the importing right now.
Working on a fix for the importing right now.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: 2015r2.0 LDAP woes
Yep, mine are all missing the "AD Username". 40 users to correct, I'll go grab another cup of coffee... 
Andrew J. - Do you even grok?
Re: 2015r2.0 LDAP woes
Also, my AD account is listed as an Admin, but when I login, no admin functions are visible.
Andrew J. - Do you even grok?
Re: 2015r2.0 LDAP woes
It doesn't pull your authentication level based on the AD level - it's specifically set in Log Server when you do the import on the last page but you will have to go through and set the ones you want to be admins to admins if you didn't on the import page. Unless you mean it's set as admin in Log Server and not logging in with admin permissions?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.