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).
Shape the future of IBM!
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Better errors notification or commands to diagnose LDAP problem in HMC.
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.
Do not place IBM confidential, company confidential, or personal information into any field.