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 Feb 21, 2018

Allow unencrypted password in an SSL conversation

This is a request to align the behavior of DB2 LUW with that of IBM i and DB2 for z/OS when connecting with a DRDA client.

With the other 2 platforms, if DRDA is configured to require user/password to be sent encrypted with minimum encryption level *AES, clients can send the user/password as unencrypted if the entire conversation is encrypted in SSL.

However, this does not appear to be the case with DB2 LUW - the documentation is silent on the matter, and my experiment (using non-encrypted user & password in an SSL stream) showed failure.


DB2 for z/OS:

default is NO (SERVER)

A user ID and password are required for connection requests. Kerberos tickets are also accepted. In addition, one of the following must be true:
The user ID and password is AES (Advanced Encryption Standard)-encrypted.
===> The connection is accepted on a port that ensures AT-TLS (Application Transparent - Transport Layer Security) policy protection, such as a Db2 security port (SECPORT). <=====


IBM i:

The DDM and DRDA® TCP/IP server supports the following forms of password encryption:
Password substitute algorithm
Diffie-Hellman public key algorithm (56 bit *DES or 256 bit *AES)
A strong password substitute algorithm
The client and server negotiate the security mechanism that will be used, and any of the three encryption methods will satisfy the requirement of encrypted password (PWDRQD(*USRENCPWD)),
===> as does the use of Secure Sockets Layer (SSL) data streams ===> .


If you specify PWDRQD(*USRENCPWD) on the Change DDM TCP/IP Attributes (CHGDDMTCPA) command, you can use any valid password along with SSL. This is possible because the system recognizes that the whole data stream, including the password, is encrypted.