THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Type | Default | Possible Values | Description | |
|---|---|---|---|---|
topic.tracking.enable | boolean | true | true, false | Whether the Connect worker will track and persist which topics are actively used per connector. It's highly recommended to set the same value in all the workers of a Connect cluster |
topic.tracking.allow.reset | boolean | true | true, false | Whether to allow requests to reset the set of active topics for specific connectors. |
Security
This feature enables a user or application to find out the topic names that are used by a connector. With respect to security, this feature inherits the security characteristics that similar functionality has in Kafka Connect at the moment. Specifically:
- A user that has the ability to query the status, create or reconfigure a connector via the Connect REST API will be able to get the set of topic names that a connector uses. If access to specific endpoints is restricted for certain users, the Connect cluster administrators should consider restricting access to the new endpoints in a similar way.
- The topic names that a connector uses, are persisted in the
status.storage.topic. This is an existing internal topic for Kafka Connect. Administrators should restrict access to the sets active topics per connector in the same way that they currently restrict access to the configuration and the status of connectors in their Connect clusters.
Given the above, the implementation of this KIP does not require extra steps to secure access to the set of active topic names that connectors are using.
Compatibility, Deprecation, and Migration Plan
...