This is an IBM Automation portal for Cloud Management and AIOps products. 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
Today we solved the ldap authentication problem. It was due to a conflict of two users with the same username in two different user repositories: basic and LDAP. Since there is no more a local user repository in Liberty a copy of your real installation user is created in the file registry when 9.5 is installed. Normally it’s not causing any problem since the user is a local user, in this case the user is an Active Directory user so, when adding ldap active Directory authentication, the user resulted as duplicated and it’s not supported. The fix was to change the name of the basic user, the basic user is used only as an authorization account to stop and start Liberty so no impact on the scheduling for the change. Why the problem did not occure in 9.4? In 9.4 on windows the default user registry was basic and local, since local os repository is installed no copy of this user has been created. When switching to the LDAP Active Directory in 9.4 the local OS was excluded (the error recieved was typical for 9.4 users that were switching to active directory without excluding local OS), basic registry cannot be excluded anyway. A NICE TO HAVE: Having a separate parameter different from wauser in the installation to specify the liberty user would be very nice and would have avoided the duplicate user problem.
Do not place IBM confidential, company confidential, or personal information into any field.