Unsolved
This post is more than 5 years old
5 Posts
0
6043
April 12th, 2018 01:00
LDAP Configuration for PowerEdge R930/R730
I was trying to configure LDAP authentication on DELL iDrac since long time and failed every time. (so we have created local user with password repo)
This is what I have configured (Tried different combo as well)
And when I test with a valid user, it will end up like this.
02:35:46 Test user authenticated user= host=linux.example.com
02:35:46 Search command:
Bind DN: [Anonymous]
Scope: subtree
Base DN: OU=User Accounts,OU=User Directory,DC=linux,DC=example,DC=com
Search filter: (memberUid=john)
Attribute list:
objectClass
memberOf
dn
uid
objectCategory
defaultNamingContext
namingContexts
ldapServiceName
supportedControl
supportedExtension
02:35:47 ERROR: Find the user DN by performing a subtree search - Operations error
Any idea ?
Note : Same config is perfectly working in all HPE servers.


ginigangadharan
5 Posts
0
April 12th, 2018 21:00
@Anonymous, Thanks you for the reply
But I have already tried that. (as attached screenshot)
Seems, the actual configuration need to be explained. (Like what should be the value given as CN/DN etc)
RRRRRR5
1 Message
0
June 26th, 2018 07:00
I'm getting the exact same error trying to configure the iDRAC for LDAP authentication and have selected not to use certificates. I agree the documentation doesn't give examples nor explain any of the details to help give direction on what is needed.
Connecting to ldaps://[XXXXXX.org]:636...
08:29:32 Test user authenticated user= host=XXXXXX.org
08:29:32 Search command:
Bind DN: [Anonymous]
Scope: subtree
Search command:
Bind DN: [Anonymous]
Scope: subtree
Base DN: OU=XXXXXX,DC=XXXXXXX,DC=org
Attribute list:
objectClass
memberOf
dn
uid
objectCategory
defaultNamingContext
namingContexts
ldapServiceName
supportedControl
supportedExtension
08:29:32 ERROR: Find the user DN by performing a subtree search - Operations error
DELL-Shine K
6 Operator
•
3K Posts
0
June 26th, 2018 08:00
Can you share the below details
Olly_H
1 Message
0
February 3rd, 2020 17:00
Here is what worked for us:
"Use Distinguished Name to Search Group Membership" needs to be set to "Yes"
Bind DN/Bind Password will need a user or service account that has the right to bind
Attribute of User Login should be set to "sAMAccountName"