#Unsuccessful AD/LDAP integration for "NAbox-4.0.10.ova"

1 messages · Page 1 of 1 (latest)

silk ibex
#

Hi team,

I am unsuccessfully integrating AD/LDAP with "NAbox-4.0.10.ova". I followed the configuration guide from the below page. My AD team confirmed all provided info was correct but still could not integrate after selecting "Save" button. However, without a test button to test AD/LDAP integration, I don't know if it is something wrong with the box or the info given was incorrect. Is there any LDAP integration fails logs we can check for this OVA? Thanks.

https://nabox.org/documentation/configuration/#ldap-active-directory

plain drift
#

How are you trying to log in ? LDAP integration is only for Grafana, not NAbox admin

silk ibex
#

That is correct. Aftrer setting up for NAbox, loggin into Grafana using AD authenicated username & pw but kept receiving invalid.

image.png
#

Here's the provided info by AD team.

image.png
plain drift
#

I think some DN fields are very picky regarding spaces after comma.

You can log into Grafana as admin, and go in the ldap test section to see what error you’re getting there.

#

Definitely a test button would be a great help, I’ll add an issue for this.

silk ibex
#

I just removed all the spaces after the comma. Logged into Grafana as admin & tested user mapping and failed. NAbox is pingable to LDAP server though.

image.png
plain drift
#

From the screenshot I would have thought there weren’t any spaces

#

Also I think the username alone should be searched for but you probably tried that

silk ibex
#

Yes, I'd tried configuring both with spaces or without & searching with just name or "domain\name" & still not working. Any CLI command to check /var/logs for LDAP configuration issue?

plain drift
#

You can try dc logs -f grafana yes

silk ibex
#

"dc logs -f grafana" was not helpful at all in troubleshooting. Do I have to have SSL configured in order for LADP/AD integration to work? Would checking "Insure TLS" or "STARTTLS" help? Or maybe we can jump on a Teams call to make sure I configured correctly?

plain drift
#

It seems communication is correct and the user is not found. We can do teams next week yes. I’m sending you an invite

jolly bear
#

dc logs wasn't any help?
Did it at least show you that an attempt was being made to connect?
And for the TLS/etc you need to check with your guys to see if that is required on your AD system.
One of our domains is set to require tls/ssl and another one is open (test env for security testing).
NABox works just fine with both of them.

silk ibex
#

@plain drift please help to send over meeting invite on either Monday, Tuesday or Wednesday morning after 8 AM PST so I can forward the invite to AD team as well to have them on the call. Thanks.

plain drift
#

Sorry I forgot to attach recipients

silk ibex
#

@plain drift Thank you very much for your help.

nova jay
#

Hello all, was there utlimately solution for this issue? It might help reolve my issue, if the non secret resolution can be shared 🙂