This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
We are beginning to use LDAP to authenticate admins who are using the HMC, but are not having success.
We don't see any problems when using local authentication.
I have tested our LDAP settings from a Linux host with the "ldapsearch" tool available, and I can look up account details using the credentials
of the BindDN that has been provided to us.
When I update my user on the HMC to authenticate by LDAP, I am able to
login - but with the previous local password, not the LDAP password. I
do not see any errors in the Console Events log.
It turns out our issue was a typo in the LDAP connection strings, which
is something you can stare at for hours and not see. But I still need to
see if there's a better way we could have caught that.
Can you check to see if there is any way we can get additional
information out of the LDAP configuration on a HMC? I would love to see
a "cannot login using bind account" or "user xxx did not match search
criteria, denying login" message.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Please see previous comments on ldapsearch option. If that doesn't address your requirement, please re-open with more info.
Thanks.
Hi,
ldapsearch can be used to validate the ldap settings and to get to know the errors. Please find below some examples of the same. Please let us know if this addresses the requirement.
Valid Scenario :
cmd -> ldapsearch -h 9.194.251.135 -D cn="",cn=Users,dc=corp,dc=ibm,dc=com -w -b cn=Users,dc=corp,dc=ibm,dc=com "cn=" -v
ldap_initialize( ldap://9.194.251.135 )
filter: cn=
requesting: All userApplication attributes
# extended LDIF
#
# LDAPv3
# base with scope subtree
# filter: cn=phani
# requesting: ALL
#
.......
..
Invalid Credentials :
1. Space on bind dn string
cmd -> ldapsearch -h ip -D cn="",cn=Users,dc=corp,dc =ibm,dc=com -w -b cn=Users,dc=corp,dc=ibm,dc=com "cn=" -v
ldap_initialize( ldap://ip )
ldap_bind: Invalid credentials (49)
additional info: 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1
2. Invalid username/password of user who is going to bind the connection
cmd -> ldapsearch -h ip -D cn="",cn=Users,dc=corp,dc=ibm,dc=com -w -b cn=Users,dc=corp,dc=ibm,dc=com "cn=" -v
ldap_initialize( ldap://ip )
ldap_bind: Invalid credentials (49)
additional info: 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1
Invalid search filter :
1. Space on search filter string
cmd -> ldapsearch -h ip -D cn="",cn=Users,dc=corp,dc=ibm,dc=com -w -b cn=Users,dc= corp,dc=ibm,dc=com "cn=" -v
ldap_initialize( ldap://ip )
filter: =ibm,dc=com
requesting: cn=phani
# extended LDIF
#
# LDAPv3
# base with scope subtree
# filter: =ibm,dc=com
# requesting: cn=phani
#
ldap_search_ext: Bad search filter (-7)
2.
cmd -> ldapsearch -h ip -D cn="",cn=Users,dc=corp,dc=ibm,dc=com -w -b cn= Users,dc=corp,dc=ibm,dc=com "cn=" -v
ldap_initialize( ldap://ip )
filter: Users,dc=corp,dc=ibm,dc=com
requesting: cn=phani
# extended LDIF
#
# LDAPv3
# base with scope subtree
# filter: Users,dc=corp,dc=ibm,dc=com
# requesting: cn=phani
#
Creating a new RFE based on Community RFE #81594 in product Power Hardware Management Console.