"LDAP username cannot be empty" error on LDAP / AD setup | NetApp | Page 1

static elk Apr 29, 2025, 10:11 AM

#

Hello guys !

Got a small issue with Nabox 4.0.10, LDAP authentication against AD used to work but does not anymore post-upgrade, and everytime I try to validate the setup.

Obviously, the ldap username / bind DN is NOT empty, so I smell either a red herring... or a bug 🙂

Anyone has an idea about something I did wrong ?

Thanks!

#

LDAP authentication directly from Nabox's shell seems to work OK:

harvest-cust /etc # ldapwhoami -x -W -H "ldaps://10.0.230.1" -D "CN=SVC-LDAP-USER,OU=Service Accounts,OU=Admin,OU=CORP,DC=user,DC=redacted,DC=net" -o "TLS_REQCERT=allow"
Enter LDAP Password:
u:USER\SVC-LDAP-USER

young fiber Apr 29, 2025, 11:36 AM

#

You're getting an error that username is empty ?

young fiber Apr 29, 2025, 12:01 PM

#

There is actually a bug with data validation but it's too permissive anyways

#

I'm failing to see the error in your screenshot is what I'm saying 🙂

static elk Apr 29, 2025, 1:33 PM

#

Oh yeah, it is not in the screenshot actually, it displays as a flash message during save

#

Here you go

young fiber Apr 29, 2025, 2:33 PM

#

Got it

young fiber Apr 29, 2025, 3:38 PM

#

can you flip sAMAccountName off and on (select another entry and back

static elk Apr 29, 2025, 10:41 PM

#

Well played, I thought given the error that the problem was with the Bind DN, not the username attribute name :p

#

That's a Nabox 3 migrated installation, the format of the label / value changed between 3 and 4 ?

young fiber Apr 30, 2025, 8:16 AM

#

There was a slight change in 4.0.10 in the way LDAP attributes are passed 😦

#

I'm guessing it is fixed now, even subsequent changes

static elk Apr 30, 2025, 9:53 AM

#

Aight, works for me 🙂

#"LDAP username cannot be empty" error on LDAP / AD setup