The customer has a restricted security policy for the DB2 server which is used as the XMeta repository.
DB2 Database MANAGER AUTHENTICATION = SERVER_ENCRYPT
DB2AUTH = JCC_ENFORCE_SECMEC
As a result of the DB2 configuration Microservice pods with metadata repository connections are not starting with CrashBackOffLoop status.
|Who would benefit from this IDEA?||Customers installing the Microsevices tier with a restricted security policy for the DB2 server would benefit from this idea|
How should it work?
Need to add JCC_ENFORCE_SECMEC to the DB2AUTH for product implementation
|Priority Justification||Customers with a restricted security policy for the DB2 server which is used as the XMeta repository will experience an issue installing the Microservices tier|
|Customer Name||Royal Bank|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions