nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Setting up LDAP on SolidFire 9.3

JMPALUCH13

I am following the instuctions to setup LDAP on SolidFire but I am gettin gthe error of LDAP search failed when I test a user login. The direct bind option does not work either. I am not sure if the syntax is correct for the settings of Search Bind DN or user DN template. Anybody have any suggestions?

Thanks

Find more posts tagged with

Accepted answers

Sahana

Hi,

Please refer EnableLdapAuthentication on page 168 in https://library.netapp.com/ecm/ecm_get_file/ECMLP2839249

All comments

elementx

Can you provide the following info:

a) Element OS version

b) LDAP back end info (AD, OpenLDAP, etc.)

c) Settings you used

JMPALUCH13

a) Element OS version --- 9.3

b) LDAP back end info (AD, OpenLDAP, etc.) ---- AD

c) Settings you used

user search filter === (objectClass=person)(sAMAccountName=%USERNAME%))

auth type ==== search and bind

group search type ========= AD

Sahana

Hi,

Please refer EnableLdapAuthentication on page 168 in https://library.netapp.com/ecm/ecm_get_file/ECMLP2839249

elementx

As Sahana suggested, take a look at the AD example in the docs.

userSearchBaseDN and few other things you didn't mention are given in there.

It's faster to try by using the API or CLI (PowerShell or Python) because you don't have to click and type a ton of times to retry.

parisi

There are two places where LDAP can fail - bind and search.

Bind is the login portion, which gives you access to search. Sounds like that's working for you.

Search can fail for a number of reasons:

- wrong search scope

- wrong base DN specified

- incorrect LDAP schema attributes specified

- object doesn't exist/isn't populated with UNIX attributes in AD

There's no way to resolve this issue without the details asked for in previous posts. We'd need the DN specified, the schema being used and Powershell output of the AD object being queried.

For example: Get-ADUser {name} -properties *

elementx

Video walk-through

https://www.youtube.com/watch?v=IY8ooGMSaOA