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,
Post an idea
Upvote ideas that matter most to you
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.
Multifactor Authentication Support for db2connectactivate utility execution on z/OS Db2
We have a large amount of z/OS Db2 workload initiated from remote connections. Initially we used Db2 Connect servers to facilitate those connections but have recently moved to direct connections whicWackage. We use the db2connectactivate utility to create the SP and bind the package and need to run it for the V11.5 license. Our audit/compliance rules require us to use a Multifactor Authentication ID for any elevated access. This MFA ID must be checked out daily and requires a password which has a token component that changes every 30 seconds. The db2connectactivate utility drops/recreates the SYSIBM.DB2CON_LIC SP and rebinds the DB2LIC.SYSLIC package. When we run that utility with our MFA ID, the DB2LIC.SYSLIC rebind fails with an authentication error because it is trying to establish a new connection with the MFA credentials that have now expired.
We are requesting MFA support within the db2connectactivate utility which would allow both the drop/recreate of the SYSIBM.DB2CONLIC SP and DB2LIC.SYSLIC bind to occur as part of a single connection so the original credentials will be used. Today we are unable to enable the V11.5 license in Production because we cannot manually bind the DB2LIC.SYSLIC which is the piece that is failing on the second connection.
This license is crucial for our remote workload and MFA IDs are required for the level of access this utility needs to complete the drop/recreate/bind processes. We are asking for the db2connectactivate utility to be redesigned to support the use of an MFA ID.
Do not place IBM confidential, company confidential, or personal information into any field.