Securing connections for Talend Dictionary Service

Procedure

Open the dq_dict/config/data-quality.properties file.

Since R2024-05, configure MongoDB SSL using these settings:

spring.ssl.bundle.jks.mymongodbssl.location=/path/to/mongodb-keystore.jks
spring.ssl.bundle.jks.mymongodbssl.password=yourKeystorePassword

To enable SSL for MongoDB and apply the SSL bundle, update your configuration as follows:

spring.data.mongodb.ssl.enabled=true
spring.data.mongodb.ssl.bundle=mymongodbssl

To secure connections with Kafka using communication encryption only, edit the following lines:
```
spring.cloud.stream.kafka.binder.configuration.security.protocol=SSL
```

Uncomment and edit the following lines:

spring.cloud.stream.kafka.binder.configuration.ssl.truststore.location=<path_to_truststore>
spring.cloud.stream.kafka.binder.configuration.ssl.truststore.password=<truststore_password>

To secure connections with Kafka using authentication, uncomment and edit the following lines:

spring.cloud.stream.kafka.binder.configuration.ssl.keystore.location=<path_to_keystore>
spring.cloud.stream.kafka.binder.configuration.ssl.keystore.password=<keystore_password>
spring.cloud.stream.kafka.binder.configuration.ssl.key.password=<key_password>

To secure connections with Talend Identity and Access Management, change the below URLs from http to https:
```
oidc.url=https://<iam_url:port>/oidc
scim.url=https://<iam_url:port>/scim
```
Note that the communication encryption parameters must also be defined to use authentication.

Results

Talend Dictionary Service only supports the Java Key Store (.jks) format to store keys and certificates.

To enable SSL support on MongoDB, see Configure mongod and mongos for TLS/SSL in the MongoDB documentation.

To enable SSL support on Kafka, see Encryption and Authentication using SSL in the Kafka documentation.

To enable SSL support on Talend Identity and Access Management, see Securing connections for Talend Identity and Access Management.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here