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 Planned for future release
Workspace Db2
Created by Guest
Created on Jun 25, 2020

Allow use of two factor authentication using smart cards for authentication for ODBC

Security requirements make us move to use two factor authentication when accessing Db2 for z/OS. We do have everything set up for the server side by using AT-TLS ServerWithClientAuth configuration for our Db2 for z/OS systems.

We can also make Db2 Connect talk to the MSCAPI via GSKit. But there is a missing part to be able to keep the certificate and its private key on the smart card. This is due to the ODBC driver requiring a clientlabel for certificate(client) authentication. As we understand it, the clientlabel is something you add to a certificate in your local keystore in order to being able to reference it and distinguish it from other certificates stoed in the local keystore.

Since our physical client certificates has to stay in the smart card (not to be stored in a local keystore) to provide true multi factor authentication, there is no possibility to locally add a label - and a label is not an X .509 attribute that can be put into a certificate by a certificate authority.

Needed by Date Jun 29, 2020