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.
enable catalog database with SECURITY SSL in LDAP (MS active directory)
After enabling ssl for connections to db2 we want to register (catalog) database in Microsoft active directory (LDAP) to provide it to all user.
But "db2 register db2 server in ldap as DATABASE protocol tcpip hostname hosta svcename 50005 SECURITY SSL remote hosta instance dbinst2 ostype Linux"
Fails with "SQL3263N The protocol type is not supported".
Workaround would be local catalog tcpip node with security ssl and database on each client, but we normaly use central catalog information in MS AD, so this would be a complete return to the past before LDAP-catalog.
CaseID TS003353378 says
•REGISTER DB2 SERVER IN LDAP & CATALOG LDAP NODE
•Do not support Db2 server using TLS
•Do not support communicating with LDAP over TLS
•You will need to catalog the TCPIP node directly on each client
Do not place IBM confidential, company confidential, or personal information into any field.