Skip to Main Content
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 Not under consideration
Workspace Db2
Components Security
Created by Guest
Created on Oct 28, 2019

Allow to switch off username conversion to lowercase

We are currently using Db2, SLES11, RACF/LDAP (zOS). Application users (personalized users, not system users) connecting to Db2 are defined in RACF/LDAP.


Db2 user authentication and authorization is using Transparent LDAP, accessing RACF/LDAP. The usernames in RACF/LDAP are defined using uppercase letters, e.g. S123456 (zOS). DB2 privileges like "connect, select, update ..." are granted to LDAP groups, but not the primary group of a user. (System users like Db2 instance users and administration users (performing loads into DB2) are managed locally on Liunux by /etc/passwd.)


This architecture worked well using SLES11, after Linux migration to SLES12 it did not work anymore. The reason is on the one hand SLES12 is not case insensitive regarding usernames anymore, SLES11 was case insensitive (the changed behavior is treated as a correction by SuSE). On the other hand it was found out Db2 is converting usernames always to lowercase, e.g. Db2 converts username [S123456] to [s123456] for groupset enumeration.


Thus, if Db2 establishes a connection using conversion  "lower(username)" the secondary groups of username are not returned by LDAP, leading to missing permissions. User/password authenticatoin  is working this way, but not evaluating the secondary groups. If Db2 would provide a way (e.g. Db2 registry variable) to switch off the conversion of the username, RACF/LDAP  would return the complete user group-list. See Db2 case TS002722481 (and Linux case TS002758643, TS002764890).

Needed by Date Nov 30, 2019