Creating secrets to protect sensitive Db2 SSL configuration data
If you plan to use SSL for your Db2® database, create a secret manually to protect the certificate data for the database.
Before you begin
If you plan to use SSL for your Db2® database, create a secret manually to protect the certificate data for the database.
Procedure
What to do next
The following values specify the SSL database configuration and
provide the name of the SSL secret that you created:
dc_ssl_enabled: true
database_ssl_secret_name: "<db ssl secret name>"
For example, for the
relevant datasource for your IBM FileNet® Content
Manager deployment, your CR might look
like the following sample snip:
datasource_configuration:
# the candidate value is "db2" or "db2HADR" or "oracle" or "sqlserver"
dc_ssl_enabled: true
dc_gcd_datasource:
dc_database_type: "db2"
...
database_ssl_secret_name: "ibm-db2-ssl-cert-secret"
dc_os_datasources:
- dc_database_type: "db2"
...
database_ssl_secret_name: "ibm-db2-ssl-cert-secret"
Also remember to add the
database user name and password to the ibm-fncm-secret
.