- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- LDAP - bind dn
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2011 08:32 AM
тАО01-11-2011 08:32 AM
I'm trying to configure Onboard Administrator to login using my LDAP.
The thing is my users dn are like
uid=resteves,ou=People,dc=vi,dc=pt
And from what i see in the ldap logs OA tries do bind with :
[11/Jan/2011:16:23:18 +0000] conn=12274 op=1 BIND dn="cn=resteves,ou=People,dc=vi,dc=pt" method=128 version=2
which fails.
Anyway to specify which ldap field to use as user? Use uid instead of cn?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2011 12:16 PM - last edited on тАО11-10-2011 01:37 PM by Kevin_Paul
тАО01-11-2011 12:16 PM - last edited on тАО11-10-2011 01:37 PM by Kevin_Paul
Re: LDAP - bind dn
hello Ricardo,
try the following:
http://h30499.www3.hp.com/t5/HP-BladeSystem/onboard-administrator-directory-groups/m-p/5030801#M13981
there is a word doc!
andras
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2011 12:30 PM
тАО01-11-2011 12:30 PM
Re: LDAP - bind dn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2011 02:28 AM
тАО01-12-2011 02:28 AM
Re: LDAP - bind dn
Then problem is that my users are for example:
dn="uid=resteves,ou=People,dc=vi,dc=pt"
and OA searches for:
dn="cn=resteves,ou=People,dc=vi,dc=pt"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2011 05:37 PM
тАО01-12-2011 05:37 PM
SolutionYep OA is not aware of UID. You need to create users as part of inetOrgPerson object class and that should get you past any authentication issues. But, then you will have authorization issues. The id must also be part of object class "user" and have a "groupMembership" attribute with the OA groups the user can access. If the object class "user" and attribute "groupMembership" does not exist in Fedora then it needs to be added.