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
|Who would benefit from this IDEA?||All clients using ssl-connections.|
How should it work?
db2 register db2 server in ldap as DATABASE protocol tcpip hostname hosta svcename 50005 SECURITY SSL remote hosta instance dbinst2 ostype Linux
|Priority Justification||Important functionality and requirement for using ssl security for Db2 connections|