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 Under review
Created by Guest
Created on Sep 21, 2021

Windows Db2-Runtime-Client with Certificate authentication: should also work without specifying sslClientLabel

Windows Db2-Runtime-Client with Certificate authentication: should also work without specifying sslClientLabel

Today it is mandatory to define sslClientLabel (aka Friendly Name) if SSLClientKeystoredb value="GSK_MS_CERTIFICATE_STORE" is set.

We have over 50,000 employees in our company and the "Friendly Name" is not set in the MS Certificate Store.

Even when the Friendly Name would be set (for example to the users name), the db2dsdriver.cfg file will look different for every user.

It must be possible to have a common db2dsdriver.cfg file for all users WITHOUT sslClientLabel set.

The certificate access should work as follows:

- If only one certificate is available in the MS certificate store, this certificate must be used.

- If more than one certificates is available, a selection prompt must appear to give the user the choice to select the right one.

Therefore, please implement that the PARM sslClientLabel is OPTIONALLY.

Actually like with a JDBC connection; there it also works without specifying a label.

Needed By Yesterday (Let's go already!)
  • Guest
    Oct 5, 2021

    Java driver uses JDK for ssl implementation and Non-Java driver uses IBM gskit library for ssl implementation. JDK supports separate keystore and truststore. Hence it is possible to use keystore for storing client certificate and truststore for storing server cerificate. So JDK knows that the certificate present in keystore is the client certificate that need to be send during connection, hence no need to specify the clientlabel from a jdbc application.

    But GSKit does not have separate trust store and keystore. There is only one keydb for storing both client certificate and server certificate. Hence it is mandatory for the non-jdbc application to identify the client certificate that need to be picked from keydb during connection using clientlabel keyword.

    There are 2 possible solutions for your scenario. You could try one of the below.

    1) Provide the same client label name(Eg:test) for all the users while adding/importing the certificate to the keydb. This way, all users can use the same db2dsdriver.cfg file where clientlabel will point to the same label name(Eg:test).

    2) If there is a default friendly name(label) for the certificate added/imported to the keydb and If this default friendly name(label) is same for all users, you can specify this default friendly name(label) as clientlabel in db2dsdriver.cfg file and use the same db2dsdriver.cfg for all users.

    Below is an example of a certificate with sample friendly name in keydb

    - "cn=test user##13:0:0:94:5c:b2:1f:c3:cc:3a:7d:39:63:0:0:0:0:94:5c##CN=IBM Issuing CA,DC=IBM,DC=com"

    The string before ## is the default friendly name. ie. cn=test user

    You can use the below command to list certificates/label names

    gsk8capicmd_64 -cert -list -db GSK_MS_CERTIFICATE_STORE