You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -109,6 +109,15 @@ There are three basic converters built into Apache Kafka, with the likely useful
109
109
In addition, there is another converter for the Avro format that is part of the Confluent Platform. This has not been tested with the MQ source connector at this time.
110
110
111
111
112
+
## Security
113
+
The connector supports authentication with user name and password and also connections secured with TLS using a server-side certificate. It does not currently support TLS mutual authentication with client-side certificates.
114
+
115
+
### Setting up TLS using a server-side certificate
116
+
To enable use of TLS, set the configuration 'mq.ssl.cipher.suite' to the name of the cipher suite which matches the CipherSpec in the SSLCIPH attribute of the MQ server-connection channel. Use the table of supported cipher suites for MQ 9.0.x [here](https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q113220_.htm) as a reference. Note that the names of the CipherSpecs as used in the MQ configuration are not necessarily the same as the cipher suite names that the connector uses. The connector uses the JMS interface so it follows the Java conventions.
117
+
118
+
You will need to put the public part of the queue manager's certificate in a JSSE truststore and then provide the location of the truststore as property to the Kafka Connect worker that you're using to run the connector.
119
+
120
+
112
121
## Configuration
113
122
The configuration options for the MQ Source Connector are as follows:
114
123
@@ -121,19 +130,24 @@ The configuration options for the MQ Source Connector are as follows:
121
130
| mq.user.name | The user name for authenticating with the queue manager | string || User name |
122
131
| mq.password | The password for authenticating with the queue manager | string || Password |
123
132
| mq.message.body.jms | Whether to interpret the message body as a JMS message type | boolean | false ||
133
+
| mq.ssl.cipher.suite | The name of the cipher suite for TLS connection | string || Blank or valid cipher suite |
124
134
| topic | The name of the target Kafka topic | string || Topic name |
125
135
126
136
127
137
## Future enhancements
128
-
The first version of the connector is intentionally basic. The idea is to enhance it with additional features to make it more capable. Some possible future enhancements are:
129
-
* TLS connections
138
+
The connector is intentionally basic. The idea is to enhance it over time with additional features to make it more capable. Some possible future enhancements are:
139
+
* TLS mutual authentication
130
140
* Message key support
131
141
* Configurable schema for MQ messages
132
142
* JMX metrics
133
143
* JSON parsing so that the JSON type information is supplied to the converter
134
144
* Testing with the Confluent Platform Avro converter and Schema Registry
135
145
136
146
147
+
## Issues and contributions
148
+
For issues relating specifically to this connect, please use the [GitHub issue tracker](https://github.com/ibm-messaging/kafka-connect-mq-source/issues). If you do submit a Pull Request related to this connector, please indicate in the Pull Request that you accept and agree to be bound by the terms of the [IBM Contributor License Agreement](CLA.md).
0 commit comments