IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Workspace SPSS Modeler
Created by Guest
Created on Feb 7, 2020

Ldap setting to force username to lower - Hadoop requirement

We have alpha numeric user id's which AD returns as Upper case 


1. when you look up a user "b1234", AD returns "B1234"

2. the cloudera cluster spss analytical server is trying to inter-phase with forces all user id to lowercase

3. When user impersonation is enabled on the analytical server, anaytical server updates the folder onwer permissions when it creates user temp files.  Lets look at an error to understand this better



Caused by: Permission denied: user=b1234, access=WRITE, inode=                                   "/user/as_user/analytic-root/analytic-workspace/ibm/.users/B1234/.executions/.temp/16ff7c6ce40-30ef814296c35326":B1234:hdfs:drwxr-xr-x
at org.apache.hadoop.hdfs.server.namenode.DefaultAuthorizationProvider.checkFsPermission(
so the file /user/as_user/analytic-root/analytic-workspace/ibm/.users/B1234/.executions/.temp/16ff7c6ce40-30ef814296c35326 was created by anytical server and analytical server updated the permission of the file as B1234:hdfs:drwxr-xr-x
Now since hdfs is case sensitive, it thinks both the users are different and the job fails.
4. This issue can be resolved by adding an AD attribute in AD, most organizations dont have the feasibility to do that
5. To address this issue products like Hue have added this feature as part of the product itself


Needed by Date Feb 7, 2020
  • Admin
    Oct 13, 2020

    Thanks for the suggestion. This is now delivered and a part of the latest Analytic Server 3.2.2 release (just released in late September 2020).