Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage 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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

Status Not under consideration
Created by Guest
Created on Jun 28, 2021

TS4500 LDAP auth has a flaw

User authentication up against LDAP does not work in our environment. The reason for that is that we have brackets in our AD users Display Name.
That issue was discovered in IBM case TS005232687
It is not an option to delete the brackets in our AD since it is company standard with that syntax.

Conclusion from IBM Case TS005232687
we found the problem.

You where testing with the userid "XJWTA-Admin"

What our Code does is asking the LDAP-Server for the whole USER-DN and then tries to map this to an group/role.

The Value which is returned from the LDAP-Server is not supported by our code:
[GENERIC_TEXT]
login_ldap_get_user_dn: userDN found, CN=Jesper Wagner Taanum-Willumsen (XXXXX-ADMIN),OU=IAM,OU=Administratorer ...
...
searchFilter: (&(member=CN=Jesper Wagner Taanum-Willumsen (XXXXX-ADMIN),OU=IAM,OU=Administratorer,DC=energinet,DC=local)(|(cn=Administrator)(cn=Superuser)(cn=Monitor)(cn=Service)(cn=SEC-G-Storage-group)(cn=sec-g-group)))

login_get_role: FAILED: Bad search filter
The Problem are the brackets around XXXXX-ADMIN. This is forcing our search to fail.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 5, 2021

    Customer needs to go through support channels as first instance for assessing this problem