NagiosXI- Installing AD authentication LDAP

[troytg]

Hi all,

I am evaluating Nagios XI for a monitoring solution. Installed the demo VM to our corporate neetwork etc all is fine. It discovered hosts etc and I am trying to enable AD authentication but getting some issues.

I created an AD domain user to use to bind ldap
httpd, ldap is installed and running on the nagios server.

I edited the nagios.conf and httpd.conf files and all I seem to get was a login authentication screen as Itry to connect to the console via web interface. No password/user combination I try gets me past this. So I restored the config files to normal and I can access web console again. I tried several online resources with confllicting nagios.conf settings. Some had the ldap bind user/password and some without.


Anybody know a resource or can give me the steps required to enable AD authentication on the NagiosXI VM (Centos)


Cheers

[scottwilkerson]

You shouldn't need to edit either of these files

You can download the active directory zip here
http://exchange.nagios.org/directory/Ad ... XI/details

Then upload and change the settings at Admin -> Manage Components

Additionally, if you are using SSL, you will likely need to install the AD certificate, instructions can be found here
http://exchange.nagios.org/directory/Do ... ry/details

[troytg]

Thank you for the reply. I installed and configured the components from the nagios console as per component download.

One last issue. I keep trying to change my security options to NONE instead of SSL as previously selected and it would not change.

I cant even find a button to apply settings like how it is done with LDAP etc.

[scottwilkerson]

Are you saying you don't have the Apply Settings button

ad.PNG

[troytg]

That is correct, I do not have that button present. So I cannot change security option.

[slansing]

Do you have the Apply Settings button available on any of the other Wizards in your Nagios XI server?

[troytg]

Yes it is showing on the LDAP component.

[mguthrie]

Our apologies, this was a bug that was released on this component for about 48 hours last week and has since been updated. Here's the updated version of the component.