You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by bb...@apache.org on 2026/06/24 01:50:01 UTC
(kafka-site) 01/01: Update for 4.3.1 release
This is an automated email from the ASF dual-hosted git repository.
bbejeck pushed a commit to branch docs-4.3.1
in repository https://gitbox.apache.org/repos/asf/kafka-site.git
commit 467a52230277b4fb13b91fda229ef88bf2243b30
Author: Bill <bb...@gmail.com>
AuthorDate: Tue Jun 23 21:45:45 2026 -0400
Update for 4.3.1 release
---
content/en/43/generated/admin_client_config.html | 913 -
content/en/43/generated/connect_config.html | 1333 --
content/en/43/generated/connect_metrics.html | 463 -
content/en/43/generated/connect_predicates.html | 45 -
content/en/43/generated/connect_rest.yaml | 2 +-
content/en/43/generated/connect_transforms.html | 549 -
content/en/43/generated/consumer_config.html | 1153 --
content/en/43/generated/consumer_metrics.html | 153 -
content/en/43/generated/group_config.html | 173 -
content/en/43/generated/kafka_config.html | 3776 ----
.../en/43/generated/mirror_checkpoint_config.html | 143 -
.../en/43/generated/mirror_connector_config.html | 943 -
.../en/43/generated/mirror_heartbeat_config.html | 33 -
content/en/43/generated/mirror_source_config.html | 193 -
content/en/43/generated/producer_config.html | 1133 --
content/en/43/generated/producer_metrics.html | 163 -
content/en/43/generated/protocol_api_keys.html | 159 -
content/en/43/generated/protocol_errors.html | 143 -
content/en/43/generated/protocol_messages.html | 19468 -------------------
content/en/43/generated/protocol_types.html | 35 -
.../en/43/generated/remote_log_manager_config.html | 273 -
.../remote_log_metadata_manager_config.html | 73 -
content/en/43/generated/sink_connector_config.html | 243 -
.../en/43/generated/source_connector_config.html | 243 -
content/en/43/generated/streams_config.html | 743 -
content/en/43/generated/topic_config.html | 366 -
content/en/43/getting-started/upgrade.md | 6 +-
content/en/43/operations/monitoring.md | 2 +-
content/en/43/security/authorization-and-acls.md | 2 +-
.../43/streams/developer-guide/config-streams.md | 33 +
content/en/43/streams/developer-guide/dsl-api.md | 24 +-
.../en/43/streams/developer-guide/memory-mgmt.md | 22 +
content/en/43/streams/upgrade-guide.md | 32 +-
33 files changed, 111 insertions(+), 32924 deletions(-)
diff --git a/content/en/43/generated/admin_client_config.html b/content/en/43/generated/admin_client_config.html
index ab8d891ba7..e69de29bb2 100644
--- a/content/en/43/generated/admin_client_config.html
+++ b/content/en/43/generated/admin_client_config.html
@@ -1,913 +0,0 @@
-<ul class="config-list">
-<li>
-<h4><a id="bootstrap.controllers"></a><a id="adminclientconfigs_bootstrap.controllers" href="#adminclientconfigs_bootstrap.controllers">bootstrap.controllers</a></h4>
-<p>A list of host/port pairs to use for establishing the initial connection to the KRaft controller quorum. This list should be in the form <code>host1:port1,host2:port2,...</code>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="bootstrap.servers"></a><a id="adminclientconfigs_bootstrap.servers" href="#adminclientconfigs_bootstrap.servers">bootstrap.servers</a></h4>
-<p>A list of host/port pairs used to establish the initial connection to the Kafka cluster. Clients use this list to bootstrap and discover the full set of Kafka brokers. While the order of servers in the list does not matter, we recommend including more than one server to ensure resilience if any servers are down. This list does not need to contain the entire set of brokers, as Kafka clients automatically manage and update connections to the cluster efficiently. This list must be in the [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.key.password"></a><a id="adminclientconfigs_ssl.key.password" href="#adminclientconfigs_ssl.key.password">ssl.key.password</a></h4>
-<p>The password of the private key in the key store file or the PEM key specified in 'ssl.keystore.key'.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.certificate.chain"></a><a id="adminclientconfigs_ssl.keystore.certificate.chain" href="#adminclientconfigs_ssl.keystore.certificate.chain">ssl.keystore.certificate.chain</a></h4>
-<p>Certificate chain in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with a list of X.509 certificates</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.key"></a><a id="adminclientconfigs_ssl.keystore.key" href="#adminclientconfigs_ssl.keystore.key">ssl.keystore.key</a></h4>
-<p>Private key in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with PKCS#8 keys. If the key is encrypted, key password must be specified using 'ssl.key.password'</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.location"></a><a id="adminclientconfigs_ssl.keystore.location" href="#adminclientconfigs_ssl.keystore.location">ssl.keystore.location</a></h4>
-<p>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.password"></a><a id="adminclientconfigs_ssl.keystore.password" href="#adminclientconfigs_ssl.keystore.password">ssl.keystore.password</a></h4>
-<p>The store password for the key store file. This is optional for client and only needed if 'ssl.keystore.location' is configured. Key store password is not supported for PEM format.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.certificates"></a><a id="adminclientconfigs_ssl.truststore.certificates" href="#adminclientconfigs_ssl.truststore.certificates">ssl.truststore.certificates</a></h4>
-<p>Trusted certificates in the format specified by 'ssl.truststore.type'. Default SSL engine factory supports only PEM format with X.509 certificates.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.location"></a><a id="adminclientconfigs_ssl.truststore.location" href="#adminclientconfigs_ssl.truststore.location">ssl.truststore.location</a></h4>
-<p>The location of the trust store file.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.password"></a><a id="adminclientconfigs_ssl.truststore.password" href="#adminclientconfigs_ssl.truststore.password">ssl.truststore.password</a></h4>
-<p>The password for the trust store file. If a password is not set, trust store file configured will still be used, but integrity checking is disabled. Trust store password is not supported for PEM format.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="client.dns.lookup"></a><a id="adminclientconfigs_client.dns.lookup" href="#adminclientconfigs_client.dns.lookup">client.dns.lookup</a></h4>
-<p>Controls how the client uses DNS lookups. If set to <code>use_all_dns_ips</code>, connect to each returned IP address in sequence until a successful connection is established. After a disconnection, the next IP is used. Once all IPs have been used once, the client resolves the IP(s) from the hostname again (both the JVM and the OS cache DNS name lookups, however). If set to <code>resolve_canonical_bootstrap_servers_only</code>, resolve each bootstrap address into a list of canonical n [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>use_all_dns_ips</td></tr>
-<tr><th>Valid Values:</th><td>[use_all_dns_ips, resolve_canonical_bootstrap_servers_only]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="client.id"></a><a id="adminclientconfigs_client.id" href="#adminclientconfigs_client.id">client.id</a></h4>
-<p>An id string to pass to the server when making requests. The purpose of this is to be able to track the source of requests beyond just ip/port by allowing a logical application name to be included in server-side request logging.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="connections.max.idle.ms"></a><a id="adminclientconfigs_connections.max.idle.ms" href="#adminclientconfigs_connections.max.idle.ms">connections.max.idle.ms</a></h4>
-<p>Close idle connections after the number of milliseconds specified by this config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="default.api.timeout.ms"></a><a id="adminclientconfigs_default.api.timeout.ms" href="#adminclientconfigs_default.api.timeout.ms">default.api.timeout.ms</a></h4>
-<p>Specifies the timeout (in milliseconds) for client APIs. This configuration is used as the default timeout for all client operations that do not specify a <code>timeout</code> parameter.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="receive.buffer.bytes"></a><a id="adminclientconfigs_receive.buffer.bytes" href="#adminclientconfigs_receive.buffer.bytes">receive.buffer.bytes</a></h4>
-<p>The size of the TCP receive buffer (SO_RCVBUF) to use when reading data. If the value is -1, the OS default will be used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>65536 (64 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="request.timeout.ms"></a><a id="adminclientconfigs_request.timeout.ms" href="#adminclientconfigs_request.timeout.ms">request.timeout.ms</a></h4>
-<p>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.client.callback.handler.class"></a><a id="adminclientconfigs_sasl.client.callback.handler.class" href="#adminclientconfigs_sasl.client.callback.handler.class">sasl.client.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.jaas.config"></a><a id="adminclientconfigs_sasl.jaas.config" href="#adminclientconfigs_sasl.jaas.config">sasl.jaas.config</a></h4>
-<p>JAAS login context parameters for SASL connections in the format used by JAAS configuration files. JAAS configuration file format is described <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html">here</a>. The format for the value is: <code>loginModuleClass controlFlag (optionName=optionValue)*;</code>. For brokers, the config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.service.name"></a><a id="adminclientconfigs_sasl.kerberos.service.name" href="#adminclientconfigs_sasl.kerberos.service.name">sasl.kerberos.service.name</a></h4>
-<p>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.callback.handler.class"></a><a id="adminclientconfigs_sasl.login.callback.handler.class" href="#adminclientconfigs_sasl.login.callback.handler.class">sasl.login.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL login callback handler class that implements the AuthenticateCallbackHandler interface. For brokers, login callback handler config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.callback.handler.class=com.example.CustomScramLoginCallbackHandler</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.class"></a><a id="adminclientconfigs_sasl.login.class" href="#adminclientconfigs_sasl.login.class">sasl.login.class</a></h4>
-<p>The fully qualified name of a class that implements the Login interface. For brokers, login config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.class=com.example.CustomScramLogin</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.mechanism"></a><a id="adminclientconfigs_sasl.mechanism" href="#adminclientconfigs_sasl.mechanism">sasl.mechanism</a></h4>
-<p>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>GSSAPI</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.algorithm"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.algorithm" href="#adminclientconfigs_sasl.oauthbearer.assertion.algorithm">sasl.oauthbearer.assertion.algorithm</a></h4>
-<p><p>The algorithm the Apache Kafka client should use to sign the assertion sent to the identity provider. It is also used as the value of the OAuth <code>alg</code> (Algorithm) header in the JWT assertion.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>RS256</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [ES256, RS256]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.aud"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.aud" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.aud">sasl.oauthbearer.assertion.claim.aud</a></h4>
-<p><p>The JWT <code>aud</code> (Audience) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.iss"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.iss" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.iss">sasl.oauthbearer.assertion.claim.iss</a></h4>
-<p><p>The value to be used as the <code>iss</code> (Issuer) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.jti.include"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.jti.include" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.jti.include">sasl.oauthbearer.assertion.claim.jti.include</a></h4>
-<p><p>Flag that determines if the JWT assertion should generate a unique ID for the JWT and include it in the <code>jti</code> (JWT ID) claim.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.sub"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.sub" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.sub">sasl.oauthbearer.assertion.claim.sub</a></h4>
-<p><p>The value to be used as the <code>sub</code> (Subject) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.file"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.file" href="#adminclientconfigs_sasl.oauthbearer.assertion.file">sasl.oauthbearer.assertion.file</a></h4>
-<p><p>File that contains a <em>pre-generated</em> JWT assertion.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect whenthe file changes to allow for the file to be reloaded on modifications. This allows for "live" assertion rotation without restarting the Kafka client.</p><p>The file contains the assertion in the serialized, three part JWT format:</p><ol><li>The <em>hea [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.private.key.file"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.private.key.file" href="#adminclientconfigs_sasl.oauthbearer.assertion.private.key.file">sasl.oauthbearer.assertion.private.key.file</a></h4>
-<p><p>File that contains a private key in the standard PEM format which is used to sign the JWT assertion sent to the identity provider.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect when the file changes to allow for the file to be reloaded on modifications. This allows for "live" private key rotation without restarting the Kafka client.</p><p><em>Note</em>: If a v [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.private.key.passphrase"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.private.key.passphrase" href="#adminclientconfigs_sasl.oauthbearer.assertion.private.key.passphrase">sasl.oauthbearer.assertion.private.key.passphrase</a></h4>
-<p><p>The optional passphrase to decrypt the private key file specified by <code>sasl.oauthbearer.assertion.private.key.file</code>.</p><p><em>Note</em>: If the file referred to by <code>sasl.oauthbearer.assertion.private.key.file</code> is modified on the file system at runtime and it was created with a <em>different</em> passphrase than it was previously, the client will not be able to access the private key file because the passphrase is now out of date. For that reason, when using pr [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.template.file"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.template.file" href="#adminclientconfigs_sasl.oauthbearer.assertion.template.file">sasl.oauthbearer.assertion.template.file</a></h4>
-<p><p>This optional configuration specifies the file containing the JWT headers and/or payload claims to be used when creating the JWT assertion.</p><p>Not all identity providers require the same set of claims; some may require a given claim while others may prohibit it. In order to provide the most flexibility, this configuration allows the user to provide the static header values and claims that are to be included in the JWT.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.a [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.client.credentials.client.id"></a><a id="adminclientconfigs_sasl.oauthbearer.client.credentials.client.id" href="#adminclientconfigs_sasl.oauthbearer.client.credentials.client.id">sasl.oauthbearer.client.credentials.client.id</a></h4>
-<p><p>The ID (defined in/by the OAuth identity provider) to identify the client requesting the token.</p><p>The client ID was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientId</code>. For backward compatibility, the <code>clientId</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.client.credentials.client.id</code> from conf [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.client.credentials.client.secret"></a><a id="adminclientconfigs_sasl.oauthbearer.client.credentials.client.secret" href="#adminclientconfigs_sasl.oauthbearer.client.credentials.client.secret">sasl.oauthbearer.client.credentials.client.secret</a></h4>
-<p><p>The secret (defined by either the user or preassigned, depending on the identity provider) of the client requesting the token.</p><p>The client secret was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientSecret</code>. For backward compatibility, the <code>clientSecret</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.cl [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.url"></a><a id="adminclientconfigs_sasl.oauthbearer.jwks.endpoint.url" href="#adminclientconfigs_sasl.oauthbearer.jwks.endpoint.url">sasl.oauthbearer.jwks.endpoint.url</a></h4>
-<p>The OAuth/OIDC provider URL from which the provider's <a href="https://datatracker.ietf.org/doc/html/rfc7517#section-5">JWKS (JSON Web Key Set)</a> can be retrieved. The URL can be HTTP(S)-based or file-based. If the URL is HTTP(S)-based, the JWKS data will be retrieved from the OAuth/OIDC provider via the configured URL on broker startup. All then-current keys will be cached on the broker for incoming requests. If an authentication request is received for a JWT that includes a "kid" [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwt.retriever.class"></a><a id="adminclientconfigs_sasl.oauthbearer.jwt.retriever.class" href="#adminclientconfigs_sasl.oauthbearer.jwt.retriever.class">sasl.oauthbearer.jwt.retriever.class</a></h4>
-<p><p>The fully-qualified class name of a <code>JwtRetriever</code> implementation used to request tokens from the identity provider.</p><p>The default configuration value represents a class that maintains backward compatibility with previous versions of Apache Kafka. The default implementation uses the configuration to determine which concrete implementation to create.<p>Other implementations that are provided include:</p><ul><li><code>org.apache.kafka.common.security.oauthbearer.Client [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtRetriever</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwt.validator.class"></a><a id="adminclientconfigs_sasl.oauthbearer.jwt.validator.class" href="#adminclientconfigs_sasl.oauthbearer.jwt.validator.class">sasl.oauthbearer.jwt.validator.class</a></h4>
-<p><p>The fully-qualified class name of a <code>JwtValidator</code> implementation used to validate the JWT from the identity provider.</p><p>The default validator (<code>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</code>) maintains backward compatibility with previous versions of Apache Kafka. The default validator uses configuration to determine which concrete implementation to create.<p>The built-in <code>JwtValidator</code> implementations are:</p><ul><li><code>o [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.scope"></a><a id="adminclientconfigs_sasl.oauthbearer.scope" href="#adminclientconfigs_sasl.oauthbearer.scope">sasl.oauthbearer.scope</a></h4>
-<p><p>This is the level of access a client application is granted to a resource or API which is included in the token request. If provided, it should match one or more scopes configured in the identity provider.</p><p>The scope was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>scope</code>. For backward compatibility, the <code>scope</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p> [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.token.endpoint.url"></a><a id="adminclientconfigs_sasl.oauthbearer.token.endpoint.url" href="#adminclientconfigs_sasl.oauthbearer.token.endpoint.url">sasl.oauthbearer.token.endpoint.url</a></h4>
-<p>The URL for the OAuth/OIDC identity provider. If the URL is HTTP(S)-based, it is the issuer's token endpoint URL to which requests will be made to login based on the configuration in <code>sasl.oauthbearer.jwt.retriever.class</code>. If the URL is file-based, it specifies a file containing an access token (in JWT serialized form) issued by the OAuth/OIDC identity provider to use for authorization.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="security.protocol"></a><a id="adminclientconfigs_security.protocol" href="#adminclientconfigs_security.protocol">security.protocol</a></h4>
-<p>Protocol used to communicate with brokers.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>PLAINTEXT</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [SASL_SSL, PLAINTEXT, SSL, SASL_PLAINTEXT]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="send.buffer.bytes"></a><a id="adminclientconfigs_send.buffer.bytes" href="#adminclientconfigs_send.buffer.bytes">send.buffer.bytes</a></h4>
-<p>The size of the TCP send buffer (SO_SNDBUF) to use when sending data. If the value is -1, the OS default will be used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>131072 (128 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.connection.setup.timeout.max.ms"></a><a id="adminclientconfigs_socket.connection.setup.timeout.max.ms" href="#adminclientconfigs_socket.connection.setup.timeout.max.ms">socket.connection.setup.timeout.max.ms</a></h4>
-<p>The maximum amount of time the client will wait for the socket connection to be established. The connection setup timeout will increase exponentially for each consecutive connection failure up to this maximum. To avoid connection storms, a randomization factor of 0.2 will be applied to the timeout resulting in a random range between 20% below and 20% above the computed value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.connection.setup.timeout.ms"></a><a id="adminclientconfigs_socket.connection.setup.timeout.ms" href="#adminclientconfigs_socket.connection.setup.timeout.ms">socket.connection.setup.timeout.ms</a></h4>
-<p>The amount of time the client will wait for the socket connection to be established. If the connection is not built before the timeout elapses, clients will close the socket channel. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>socket.connection.setup.timeout.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.enabled.protocols"></a><a id="adminclientconfigs_ssl.enabled.protocols" href="#adminclientconfigs_ssl.enabled.protocols">ssl.enabled.protocols</a></h4>
-<p>The list of protocols enabled for SSL connections. The default is 'TLSv1.2,TLSv1.3'. This means that clients and servers will prefer TLSv1.3 if both support it and fallback to TLSv1.2 otherwise (assuming both support at least TLSv1.2). This default should be fine for most use cases. If this configuration is set to an empty list, Kafka will use the protocols enabled by default in the underlying SSLEngine, which may include additional protocols depending on the JVM version. Also see the [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>TLSv1.2,TLSv1.3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.type"></a><a id="adminclientconfigs_ssl.keystore.type" href="#adminclientconfigs_ssl.keystore.type">ssl.keystore.type</a></h4>
-<p>The file format of the key store file. This is optional for client. The values currently supported by the default <code>ssl.engine.factory.class</code> are [JKS, PKCS12, PEM].</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>JKS</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.protocol"></a><a id="adminclientconfigs_ssl.protocol" href="#adminclientconfigs_ssl.protocol">ssl.protocol</a></h4>
-<p>The SSL protocol used to generate the SSLContext. The default is 'TLSv1.3', which should be fine for most use cases. A typical alternative to the default is 'TLSv1.2'. Allowed values for this config are dependent on the JVM. Clients using the defaults for this config and 'ssl.enabled.protocols' will downgrade to 'TLSv1.2' if the server does not support 'TLSv1.3'. If this config is set to 'TLSv1.2', however, clients will not use 'TLSv1.3' even if it is one of the values in <code>ssl.en [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>TLSv1.3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.provider"></a><a id="adminclientconfigs_ssl.provider" href="#adminclientconfigs_ssl.provider">ssl.provider</a></h4>
-<p>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.type"></a><a id="adminclientconfigs_ssl.truststore.type" href="#adminclientconfigs_ssl.truststore.type">ssl.truststore.type</a></h4>
-<p>The file format of the trust store file. The values currently supported by the default <code>ssl.engine.factory.class</code> are [JKS, PKCS12, PEM].</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>JKS</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="config.providers"></a><a id="adminclientconfigs_config.providers" href="#adminclientconfigs_config.providers">config.providers</a></h4>
-<p>Comma-separated alias names for classes implementing the <code>ConfigProvider</code> interface. This enables loading configuration data (such as passwords, API keys, and other credentials) from external sources. For example, see <a href="https://kafka.apache.org/documentation/#config_providers">Configuration Providers</a>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="enable.metrics.push"></a><a id="adminclientconfigs_enable.metrics.push" href="#adminclientconfigs_enable.metrics.push">enable.metrics.push</a></h4>
-<p>Whether to enable pushing of client metrics to the cluster, if the cluster has a client metrics subscription which matches this client.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.max.age.ms"></a><a id="adminclientconfigs_metadata.max.age.ms" href="#adminclientconfigs_metadata.max.age.ms">metadata.max.age.ms</a></h4>
-<p>The period of time in milliseconds after which we force a refresh of metadata even if we haven't seen any partition leadership changes to proactively discover any new brokers or partitions.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.recovery.rebootstrap.trigger.ms"></a><a id="adminclientconfigs_metadata.recovery.rebootstrap.trigger.ms" href="#adminclientconfigs_metadata.recovery.rebootstrap.trigger.ms">metadata.recovery.rebootstrap.trigger.ms</a></h4>
-<p>If a client configured to rebootstrap using <code>metadata.recovery.strategy=rebootstrap</code> is unable to obtain metadata from any of the brokers in the last known metadata for this interval, client repeats the bootstrap process using <code>bootstrap.servers</code> configuration.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.recovery.strategy"></a><a id="adminclientconfigs_metadata.recovery.strategy" href="#adminclientconfigs_metadata.recovery.strategy">metadata.recovery.strategy</a></h4>
-<p>Controls how the client recovers when none of the brokers known to it is available. If set to <code>none</code>, the client fails. If set to <code>rebootstrap</code>, the client repeats the bootstrap process using <code>bootstrap.servers</code>. Rebootstrapping is useful when a client communicates with brokers so infrequently that the set of brokers may change entirely before the client refreshes metadata. Metadata recovery is triggered when all last-known brokers appear unavailable s [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>rebootstrap</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [REBOOTSTRAP, NONE]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metric.reporters"></a><a id="adminclientconfigs_metric.reporters" href="#adminclientconfigs_metric.reporters">metric.reporters</a></h4>
-<p>A list of classes to use as metrics reporters. Implementing the <code>org.apache.kafka.common.metrics.MetricsReporter</code> interface allows plugging in classes that will be notified of new metric creation. When custom reporters are set and <code>org.apache.kafka.common.metrics.JmxReporter</code> is needed, it has to be explicitly added to the list.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.metrics.JmxReporter</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.num.samples"></a><a id="adminclientconfigs_metrics.num.samples" href="#adminclientconfigs_metrics.num.samples">metrics.num.samples</a></h4>
-<p>The number of samples maintained to compute metrics.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.recording.level"></a><a id="adminclientconfigs_metrics.recording.level" href="#adminclientconfigs_metrics.recording.level">metrics.recording.level</a></h4>
-<p>The highest recording level for metrics. It has three levels for recording metrics - info, debug, and trace.<br> <br>INFO level records only essential metrics necessary for monitoring system performance and health. It collects vital data without gathering too much detail, making it suitable for production environments where minimal overhead is desired.<br><br>DEBUG level records most metrics, providing more detailed information about the system's operation. It's useful for development [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>INFO</td></tr>
-<tr><th>Valid Values:</th><td>[INFO, DEBUG, TRACE]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.sample.window.ms"></a><a id="adminclientconfigs_metrics.sample.window.ms" href="#adminclientconfigs_metrics.sample.window.ms">metrics.sample.window.ms</a></h4>
-<p>The window of time a metrics sample is computed over.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="reconnect.backoff.max.ms"></a><a id="adminclientconfigs_reconnect.backoff.max.ms" href="#adminclientconfigs_reconnect.backoff.max.ms">reconnect.backoff.max.ms</a></h4>
-<p>The maximum amount of time in milliseconds to wait when reconnecting to a broker that has repeatedly failed to connect. If provided, the backoff per host will increase exponentially for each consecutive connection failure, up to this maximum. After calculating the backoff increase, 20% random jitter is added to avoid connection storms.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="reconnect.backoff.ms"></a><a id="adminclientconfigs_reconnect.backoff.ms" href="#adminclientconfigs_reconnect.backoff.ms">reconnect.backoff.ms</a></h4>
-<p>The base amount of time to wait before attempting to reconnect to a given host. This avoids repeatedly connecting to a host in a tight loop. This backoff applies to all connection attempts by the client to a broker. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>reconnect.backoff.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>50</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="retries"></a><a id="adminclientconfigs_retries" href="#adminclientconfigs_retries">retries</a></h4>
-<p>It is recommended to set the value to either <code>MAX_VALUE</code> or zero, and use corresponding timeout parameters to control how long a client should retry a request. Setting a value greater than zero will cause the client to resend any request that fails with a potentially transient error. Setting a value of zero will lead to transient errors not being retried, and they will be propagated to the application to be handled.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2147483647</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,2147483647]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="retry.backoff.max.ms"></a><a id="adminclientconfigs_retry.backoff.max.ms" href="#adminclientconfigs_retry.backoff.max.ms">retry.backoff.max.ms</a></h4>
-<p>The maximum amount of time in milliseconds to wait when retrying a request to the broker that has repeatedly failed. If provided, the backoff per client will increase exponentially for each failed request, up to this maximum. To prevent all clients from being synchronized upon retry, a randomized jitter with a factor of 0.2 will be applied to the backoff, resulting in the backoff falling within a range between 20% below and 20% above the computed value. If <code>retry.backoff.ms</code [...]
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="retry.backoff.ms"></a><a id="adminclientconfigs_retry.backoff.ms" href="#adminclientconfigs_retry.backoff.ms">retry.backoff.ms</a></h4>
-<p>The amount of time to wait before attempting to retry a failed request to a given topic partition. This avoids repeatedly sending requests in a tight loop under some failure scenarios. This value is the initial backoff value and will increase exponentially for each failed request, up to the <code>retry.backoff.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.kinit.cmd"></a><a id="adminclientconfigs_sasl.kerberos.kinit.cmd" href="#adminclientconfigs_sasl.kerberos.kinit.cmd">sasl.kerberos.kinit.cmd</a></h4>
-<p>Kerberos kinit command path.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>/usr/bin/kinit</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.min.time.before.relogin"></a><a id="adminclientconfigs_sasl.kerberos.min.time.before.relogin" href="#adminclientconfigs_sasl.kerberos.min.time.before.relogin">sasl.kerberos.min.time.before.relogin</a></h4>
-<p>Login thread sleep time between refresh attempts.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60000</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.ticket.renew.jitter"></a><a id="adminclientconfigs_sasl.kerberos.ticket.renew.jitter" href="#adminclientconfigs_sasl.kerberos.ticket.renew.jitter">sasl.kerberos.ticket.renew.jitter</a></h4>
-<p>Percentage of random jitter added to the renewal time.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.05</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.ticket.renew.window.factor"></a><a id="adminclientconfigs_sasl.kerberos.ticket.renew.window.factor" href="#adminclientconfigs_sasl.kerberos.ticket.renew.window.factor">sasl.kerberos.ticket.renew.window.factor</a></h4>
-<p>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.8</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.connect.timeout.ms"></a><a id="adminclientconfigs_sasl.login.connect.timeout.ms" href="#adminclientconfigs_sasl.login.connect.timeout.ms">sasl.login.connect.timeout.ms</a></h4>
-<p>The (optional) value in milliseconds for the external authentication provider connection timeout. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.read.timeout.ms"></a><a id="adminclientconfigs_sasl.login.read.timeout.ms" href="#adminclientconfigs_sasl.login.read.timeout.ms">sasl.login.read.timeout.ms</a></h4>
-<p>The (optional) value in milliseconds for the external authentication provider read timeout. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.buffer.seconds"></a><a id="adminclientconfigs_sasl.login.refresh.buffer.seconds" href="#adminclientconfigs_sasl.login.refresh.buffer.seconds">sasl.login.refresh.buffer.seconds</a></h4>
-<p>The amount of buffer time before credential expiration to maintain when refreshing a credential, in seconds. If a refresh would otherwise occur closer to expiration than the number of buffer seconds then the refresh will be moved up to maintain as much of the buffer time as possible. Legal values are between 0 and 3600 (1 hour); a default value of 300 (5 minutes) is used if no value is specified. This value and sasl.login.refresh.min.period.seconds are both ignored if their sum excee [...]
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.min.period.seconds"></a><a id="adminclientconfigs_sasl.login.refresh.min.period.seconds" href="#adminclientconfigs_sasl.login.refresh.min.period.seconds">sasl.login.refresh.min.period.seconds</a></h4>
-<p>The desired minimum time for the login refresh thread to wait before refreshing a credential, in seconds. Legal values are between 0 and 900 (15 minutes); a default value of 60 (1 minute) is used if no value is specified. This value and sasl.login.refresh.buffer.seconds are both ignored if their sum exceeds the remaining lifetime of a credential. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,900]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.window.factor"></a><a id="adminclientconfigs_sasl.login.refresh.window.factor" href="#adminclientconfigs_sasl.login.refresh.window.factor">sasl.login.refresh.window.factor</a></h4>
-<p>Login refresh thread will sleep until the specified window factor relative to the credential's lifetime has been reached, at which time it will try to refresh the credential. Legal values are between 0.5 (50%) and 1.0 (100%) inclusive; a default value of 0.8 (80%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.8</td></tr>
-<tr><th>Valid Values:</th><td>[0.5,...,1.0]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.window.jitter"></a><a id="adminclientconfigs_sasl.login.refresh.window.jitter" href="#adminclientconfigs_sasl.login.refresh.window.jitter">sasl.login.refresh.window.jitter</a></h4>
-<p>The maximum amount of random jitter relative to the credential's lifetime that is added to the login refresh thread's sleep time. Legal values are between 0 and 0.25 (25%) inclusive; a default value of 0.05 (5%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.05</td></tr>
-<tr><th>Valid Values:</th><td>[0.0,...,0.25]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.retry.backoff.max.ms"></a><a id="adminclientconfigs_sasl.login.retry.backoff.max.ms" href="#adminclientconfigs_sasl.login.retry.backoff.max.ms">sasl.login.retry.backoff.max.ms</a></h4>
-<p>The (optional) value in milliseconds for the maximum wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.retry.backoff.ms"></a><a id="adminclientconfigs_sasl.login.retry.backoff.ms" href="#adminclientconfigs_sasl.login.retry.backoff.ms">sasl.login.retry.backoff.ms</a></h4>
-<p>The (optional) value in milliseconds for the initial wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.exp.seconds"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.exp.seconds" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.exp.seconds">sasl.oauthbearer.assertion.claim.exp.seconds</a></h4>
-<p><p>The number of seconds <em>in the future</em> for which the JWT is valid. The value is used to determine the JWT <code>exp</code> (Expiration) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>exp</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> exp = x + y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbear [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,86400]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.nbf.seconds"></a><a id="adminclientconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds" href="#adminclientconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds">sasl.oauthbearer.assertion.claim.nbf.seconds</a></h4>
-<p><p>The number of seconds <em>in the past</em> from which the JWT is valid. The value is used to determine the JWT <code>nbf</code> (Not Before) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>nbf</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> nbf = x - y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbeare [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.clock.skew.seconds"></a><a id="adminclientconfigs_sasl.oauthbearer.clock.skew.seconds" href="#adminclientconfigs_sasl.oauthbearer.clock.skew.seconds">sasl.oauthbearer.clock.skew.seconds</a></h4>
-<p>The (optional) value in seconds to allow for differences between the time of the OAuth/OIDC identity provider and the broker.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.expected.audience"></a><a id="adminclientconfigs_sasl.oauthbearer.expected.audience" href="#adminclientconfigs_sasl.oauthbearer.expected.audience">sasl.oauthbearer.expected.audience</a></h4>
-<p>The (optional) comma-delimited setting for the broker to use to verify that the JWT was issued for one of the expected audiences. The JWT will be inspected for the standard OAuth "aud" claim and if this value is set, the broker will match the value from JWT's "aud" claim to see if there is an exact match. If there is no match, the broker will reject the JWT and authentication will fail.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.expected.issuer"></a><a id="adminclientconfigs_sasl.oauthbearer.expected.issuer" href="#adminclientconfigs_sasl.oauthbearer.expected.issuer">sasl.oauthbearer.expected.issuer</a></h4>
-<p>The (optional) setting for the broker to use to verify that the JWT was created by the expected issuer. The JWT will be inspected for the standard OAuth "iss" claim and if this value is set, the broker will match it exactly against what is in the JWT's "iss" claim. If there is no match, the broker will reject the JWT and authentication will fail.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.header.urlencode"></a><a id="adminclientconfigs_sasl.oauthbearer.header.urlencode" href="#adminclientconfigs_sasl.oauthbearer.header.urlencode">sasl.oauthbearer.header.urlencode</a></h4>
-<p>The (optional) setting to enable the OAuth client to URL-encode the client_id and client_secret in the authorization header in accordance with RFC6749, see <a href="https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1">here</a> for more details. The default value is set to 'false' for backward compatibility</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.refresh.ms"></a><a id="adminclientconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms" href="#adminclientconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms">sasl.oauthbearer.jwks.endpoint.refresh.ms</a></h4>
-<p>The (optional) value in milliseconds for the broker to wait between refreshing its JWKS (JSON Web Key Set) cache that contains the keys to verify the signature of the JWT.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms"></a><a id="adminclientconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms" href="#adminclientconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms</a></h4>
-<p>The (optional) value in milliseconds for the maximum wait between attempts to retrieve the JWKS (JSON Web Key Set) from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.ms"></a><a id="adminclientconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms" href="#adminclientconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.ms</a></h4>
-<p>The (optional) value in milliseconds for the initial wait between JWKS (JSON Web Key Set) retrieval attempts from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.scope.claim.name"></a><a id="adminclientconfigs_sasl.oauthbearer.scope.claim.name" href="#adminclientconfigs_sasl.oauthbearer.scope.claim.name">sasl.oauthbearer.scope.claim.name</a></h4>
-<p>The OAuth claim for the scope is often named "scope", but this (optional) setting can provide a different name to use for the scope included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>scope</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.sub.claim.name"></a><a id="adminclientconfigs_sasl.oauthbearer.sub.claim.name" href="#adminclientconfigs_sasl.oauthbearer.sub.claim.name">sasl.oauthbearer.sub.claim.name</a></h4>
-<p>The OAuth claim for the subject is often named "sub", but this (optional) setting can provide a different name to use for the subject included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>sub</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="security.providers"></a><a id="adminclientconfigs_security.providers" href="#adminclientconfigs_security.providers">security.providers</a></h4>
-<p>A list of configurable creator classes each returning a provider implementing security algorithms. These classes should implement the <code>org.apache.kafka.common.security.auth.SecurityProviderCreator</code> interface.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.cipher.suites"></a><a id="adminclientconfigs_ssl.cipher.suites" href="#adminclientconfigs_ssl.cipher.suites">ssl.cipher.suites</a></h4>
-<p>A list of cipher suites. This is a named combination of authentication, encryption, MAC and key exchange algorithm used to negotiate the security settings for a network connection using TLS or SSL network protocol. By default all the available cipher suites are supported.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.endpoint.identification.algorithm"></a><a id="adminclientconfigs_ssl.endpoint.identification.algorithm" href="#adminclientconfigs_ssl.endpoint.identification.algorithm">ssl.endpoint.identification.algorithm</a></h4>
-<p>The endpoint identification algorithm to validate server hostname using server certificate. </p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>https</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.engine.factory.class"></a><a id="adminclientconfigs_ssl.engine.factory.class" href="#adminclientconfigs_ssl.engine.factory.class">ssl.engine.factory.class</a></h4>
-<p>The class of type org.apache.kafka.common.security.auth.SslEngineFactory to provide SSLEngine objects. Default value is org.apache.kafka.common.security.ssl.DefaultSslEngineFactory. Alternatively, setting this to org.apache.kafka.common.security.ssl.CommonNameLoggingSslEngineFactory will log the common name of expired SSL certificates used by clients to authenticate at any of the brokers with log level INFO. Note that this will cause a tiny delay during establishment of new connection [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keymanager.algorithm"></a><a id="adminclientconfigs_ssl.keymanager.algorithm" href="#adminclientconfigs_ssl.keymanager.algorithm">ssl.keymanager.algorithm</a></h4>
-<p>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>SunX509</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.secure.random.implementation"></a><a id="adminclientconfigs_ssl.secure.random.implementation" href="#adminclientconfigs_ssl.secure.random.implementation">ssl.secure.random.implementation</a></h4>
-<p>The SecureRandom PRNG implementation to use for SSL cryptography operations. </p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.trustmanager.algorithm"></a><a id="adminclientconfigs_ssl.trustmanager.algorithm" href="#adminclientconfigs_ssl.trustmanager.algorithm">ssl.trustmanager.algorithm</a></h4>
-<p>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>PKIX</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-</ul>
-
diff --git a/content/en/43/generated/connect_config.html b/content/en/43/generated/connect_config.html
index e198d79ecf..e69de29bb2 100644
--- a/content/en/43/generated/connect_config.html
+++ b/content/en/43/generated/connect_config.html
@@ -1,1333 +0,0 @@
-<ul class="config-list">
-<li>
-<h4><a id="bootstrap.servers"></a><a id="connectconfigs_bootstrap.servers" href="#connectconfigs_bootstrap.servers">bootstrap.servers</a></h4>
-<p>A list of host/port pairs used to establish the initial connection to the Kafka cluster. Clients use this list to bootstrap and discover the full set of Kafka brokers. While the order of servers in the list does not matter, we recommend including more than one server to ensure resilience if any servers are down. This list does not need to contain the entire set of brokers, as Kafka clients automatically manage and update connections to the cluster efficiently. This list must be in the [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="config.storage.topic"></a><a id="connectconfigs_config.storage.topic" href="#connectconfigs_config.storage.topic">config.storage.topic</a></h4>
-<p>The name of the Kafka topic where connector configurations are stored</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.id"></a><a id="connectconfigs_group.id" href="#connectconfigs_group.id">group.id</a></h4>
-<p>A unique string that identifies the Connect cluster group this worker belongs to.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="key.converter"></a><a id="connectconfigs_key.converter" href="#connectconfigs_key.converter">key.converter</a></h4>
-<p>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the keys in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offset.storage.topic"></a><a id="connectconfigs_offset.storage.topic" href="#connectconfigs_offset.storage.topic">offset.storage.topic</a></h4>
-<p>The name of the Kafka topic where source connector offsets are stored</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="status.storage.topic"></a><a id="connectconfigs_status.storage.topic" href="#connectconfigs_status.storage.topic">status.storage.topic</a></h4>
-<p>The name of the Kafka topic where connector and task status are stored</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="value.converter"></a><a id="connectconfigs_value.converter" href="#connectconfigs_value.converter">value.converter</a></h4>
-<p>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="exactly.once.source.support"></a><a id="connectconfigs_exactly.once.source.support" href="#connectconfigs_exactly.once.source.support">exactly.once.source.support</a></h4>
-<p>Whether to enable exactly-once support for source connectors in the cluster by using transactions to write source records and their source offsets, and by proactively fencing out old task generations before bringing up new ones.<br>To enable exactly-once source support on a new cluster, set this property to 'enabled'. To enable support on an existing cluster, first set to 'preparing' on every worker in the cluster, then set to 'enabled'. A rolling upgrade may be used for both changes. [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>disabled</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [DISABLED, ENABLED, PREPARING]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="heartbeat.interval.ms"></a><a id="connectconfigs_heartbeat.interval.ms" href="#connectconfigs_heartbeat.interval.ms">heartbeat.interval.ms</a></h4>
-<p>The expected time between heartbeats to the group coordinator when using Kafka's group management facilities. Heartbeats are used to ensure that the worker's session stays active and to facilitate rebalancing when new members join or leave the group. The value must be set lower than <code>session.timeout.ms</code>, but typically should be set no higher than 1/3 of that value. It can be adjusted even lower to control the expected time for normal rebalances.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>3000 (3 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="rebalance.timeout.ms"></a><a id="connectconfigs_rebalance.timeout.ms" href="#connectconfigs_rebalance.timeout.ms">rebalance.timeout.ms</a></h4>
-<p>The maximum allowed time for each worker to join the group once a rebalance has begun. This is basically a limit on the amount of time needed for all tasks to flush any pending data and commit offsets. If the timeout is exceeded, then the worker will be removed from the group, which will cause offset commit failures.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="session.timeout.ms"></a><a id="connectconfigs_session.timeout.ms" href="#connectconfigs_session.timeout.ms">session.timeout.ms</a></h4>
-<p>The timeout used to detect worker failures. The worker sends periodic heartbeats to indicate its liveness to the broker. If no heartbeats are received by the broker before the expiration of this session timeout, then the broker will remove the worker from the group and initiate a rebalance. Note that the value must be in the allowable range as configured in the broker configuration by <code>group.min.session.timeout.ms</code> and <code>group.max.session.timeout.ms</code>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.key.password"></a><a id="connectconfigs_ssl.key.password" href="#connectconfigs_ssl.key.password">ssl.key.password</a></h4>
-<p>The password of the private key in the key store file or the PEM key specified in 'ssl.keystore.key'.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.certificate.chain"></a><a id="connectconfigs_ssl.keystore.certificate.chain" href="#connectconfigs_ssl.keystore.certificate.chain">ssl.keystore.certificate.chain</a></h4>
-<p>Certificate chain in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with a list of X.509 certificates</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.key"></a><a id="connectconfigs_ssl.keystore.key" href="#connectconfigs_ssl.keystore.key">ssl.keystore.key</a></h4>
-<p>Private key in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with PKCS#8 keys. If the key is encrypted, key password must be specified using 'ssl.key.password'</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.location"></a><a id="connectconfigs_ssl.keystore.location" href="#connectconfigs_ssl.keystore.location">ssl.keystore.location</a></h4>
-<p>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.password"></a><a id="connectconfigs_ssl.keystore.password" href="#connectconfigs_ssl.keystore.password">ssl.keystore.password</a></h4>
-<p>The store password for the key store file. This is optional for client and only needed if 'ssl.keystore.location' is configured. Key store password is not supported for PEM format.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.certificates"></a><a id="connectconfigs_ssl.truststore.certificates" href="#connectconfigs_ssl.truststore.certificates">ssl.truststore.certificates</a></h4>
-<p>Trusted certificates in the format specified by 'ssl.truststore.type'. Default SSL engine factory supports only PEM format with X.509 certificates.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.location"></a><a id="connectconfigs_ssl.truststore.location" href="#connectconfigs_ssl.truststore.location">ssl.truststore.location</a></h4>
-<p>The location of the trust store file.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.password"></a><a id="connectconfigs_ssl.truststore.password" href="#connectconfigs_ssl.truststore.password">ssl.truststore.password</a></h4>
-<p>The password for the trust store file. If a password is not set, trust store file configured will still be used, but integrity checking is disabled. Trust store password is not supported for PEM format.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="client.dns.lookup"></a><a id="connectconfigs_client.dns.lookup" href="#connectconfigs_client.dns.lookup">client.dns.lookup</a></h4>
-<p>Controls how the client uses DNS lookups. If set to <code>use_all_dns_ips</code>, connect to each returned IP address in sequence until a successful connection is established. After a disconnection, the next IP is used. Once all IPs have been used once, the client resolves the IP(s) from the hostname again (both the JVM and the OS cache DNS name lookups, however). If set to <code>resolve_canonical_bootstrap_servers_only</code>, resolve each bootstrap address into a list of canonical n [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>use_all_dns_ips</td></tr>
-<tr><th>Valid Values:</th><td>[use_all_dns_ips, resolve_canonical_bootstrap_servers_only]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="connections.max.idle.ms"></a><a id="connectconfigs_connections.max.idle.ms" href="#connectconfigs_connections.max.idle.ms">connections.max.idle.ms</a></h4>
-<p>Close idle connections after the number of milliseconds specified by this config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>540000 (9 minutes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="connector.client.config.override.policy"></a><a id="connectconfigs_connector.client.config.override.policy" href="#connectconfigs_connector.client.config.override.policy">connector.client.config.override.policy</a></h4>
-<p>Class name or alias of implementation of <code>ConnectorClientConfigOverridePolicy</code>. Defines what client configurations can be overridden by the connector. The default policy is <code>All</code>, meaning connector configurations can override all client properties. The other possible policies in the framework include <code>Allowlist</code> to specify allowed configurations via <code>connector.client.config.override.allowlist</code>, <code>None</code> to disallow connectors from o [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>All</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="receive.buffer.bytes"></a><a id="connectconfigs_receive.buffer.bytes" href="#connectconfigs_receive.buffer.bytes">receive.buffer.bytes</a></h4>
-<p>The size of the TCP receive buffer (SO_RCVBUF) to use when reading data. If the value is -1, the OS default will be used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>32768 (32 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="request.timeout.ms"></a><a id="connectconfigs_request.timeout.ms" href="#connectconfigs_request.timeout.ms">request.timeout.ms</a></h4>
-<p>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>40000 (40 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.client.callback.handler.class"></a><a id="connectconfigs_sasl.client.callback.handler.class" href="#connectconfigs_sasl.client.callback.handler.class">sasl.client.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.jaas.config"></a><a id="connectconfigs_sasl.jaas.config" href="#connectconfigs_sasl.jaas.config">sasl.jaas.config</a></h4>
-<p>JAAS login context parameters for SASL connections in the format used by JAAS configuration files. JAAS configuration file format is described <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html">here</a>. The format for the value is: <code>loginModuleClass controlFlag (optionName=optionValue)*;</code>. For brokers, the config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.service.name"></a><a id="connectconfigs_sasl.kerberos.service.name" href="#connectconfigs_sasl.kerberos.service.name">sasl.kerberos.service.name</a></h4>
-<p>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.callback.handler.class"></a><a id="connectconfigs_sasl.login.callback.handler.class" href="#connectconfigs_sasl.login.callback.handler.class">sasl.login.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL login callback handler class that implements the AuthenticateCallbackHandler interface. For brokers, login callback handler config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.callback.handler.class=com.example.CustomScramLoginCallbackHandler</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.class"></a><a id="connectconfigs_sasl.login.class" href="#connectconfigs_sasl.login.class">sasl.login.class</a></h4>
-<p>The fully qualified name of a class that implements the Login interface. For brokers, login config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.class=com.example.CustomScramLogin</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.mechanism"></a><a id="connectconfigs_sasl.mechanism" href="#connectconfigs_sasl.mechanism">sasl.mechanism</a></h4>
-<p>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>GSSAPI</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.algorithm"></a><a id="connectconfigs_sasl.oauthbearer.assertion.algorithm" href="#connectconfigs_sasl.oauthbearer.assertion.algorithm">sasl.oauthbearer.assertion.algorithm</a></h4>
-<p><p>The algorithm the Apache Kafka client should use to sign the assertion sent to the identity provider. It is also used as the value of the OAuth <code>alg</code> (Algorithm) header in the JWT assertion.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>RS256</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [ES256, RS256]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.aud"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.aud" href="#connectconfigs_sasl.oauthbearer.assertion.claim.aud">sasl.oauthbearer.assertion.claim.aud</a></h4>
-<p><p>The JWT <code>aud</code> (Audience) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.iss"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.iss" href="#connectconfigs_sasl.oauthbearer.assertion.claim.iss">sasl.oauthbearer.assertion.claim.iss</a></h4>
-<p><p>The value to be used as the <code>iss</code> (Issuer) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.jti.include"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.jti.include" href="#connectconfigs_sasl.oauthbearer.assertion.claim.jti.include">sasl.oauthbearer.assertion.claim.jti.include</a></h4>
-<p><p>Flag that determines if the JWT assertion should generate a unique ID for the JWT and include it in the <code>jti</code> (JWT ID) claim.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.sub"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.sub" href="#connectconfigs_sasl.oauthbearer.assertion.claim.sub">sasl.oauthbearer.assertion.claim.sub</a></h4>
-<p><p>The value to be used as the <code>sub</code> (Subject) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.file"></a><a id="connectconfigs_sasl.oauthbearer.assertion.file" href="#connectconfigs_sasl.oauthbearer.assertion.file">sasl.oauthbearer.assertion.file</a></h4>
-<p><p>File that contains a <em>pre-generated</em> JWT assertion.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect whenthe file changes to allow for the file to be reloaded on modifications. This allows for "live" assertion rotation without restarting the Kafka client.</p><p>The file contains the assertion in the serialized, three part JWT format:</p><ol><li>The <em>hea [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.private.key.file"></a><a id="connectconfigs_sasl.oauthbearer.assertion.private.key.file" href="#connectconfigs_sasl.oauthbearer.assertion.private.key.file">sasl.oauthbearer.assertion.private.key.file</a></h4>
-<p><p>File that contains a private key in the standard PEM format which is used to sign the JWT assertion sent to the identity provider.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect when the file changes to allow for the file to be reloaded on modifications. This allows for "live" private key rotation without restarting the Kafka client.</p><p><em>Note</em>: If a v [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.private.key.passphrase"></a><a id="connectconfigs_sasl.oauthbearer.assertion.private.key.passphrase" href="#connectconfigs_sasl.oauthbearer.assertion.private.key.passphrase">sasl.oauthbearer.assertion.private.key.passphrase</a></h4>
-<p><p>The optional passphrase to decrypt the private key file specified by <code>sasl.oauthbearer.assertion.private.key.file</code>.</p><p><em>Note</em>: If the file referred to by <code>sasl.oauthbearer.assertion.private.key.file</code> is modified on the file system at runtime and it was created with a <em>different</em> passphrase than it was previously, the client will not be able to access the private key file because the passphrase is now out of date. For that reason, when using pr [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.template.file"></a><a id="connectconfigs_sasl.oauthbearer.assertion.template.file" href="#connectconfigs_sasl.oauthbearer.assertion.template.file">sasl.oauthbearer.assertion.template.file</a></h4>
-<p><p>This optional configuration specifies the file containing the JWT headers and/or payload claims to be used when creating the JWT assertion.</p><p>Not all identity providers require the same set of claims; some may require a given claim while others may prohibit it. In order to provide the most flexibility, this configuration allows the user to provide the static header values and claims that are to be included in the JWT.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.a [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.client.credentials.client.id"></a><a id="connectconfigs_sasl.oauthbearer.client.credentials.client.id" href="#connectconfigs_sasl.oauthbearer.client.credentials.client.id">sasl.oauthbearer.client.credentials.client.id</a></h4>
-<p><p>The ID (defined in/by the OAuth identity provider) to identify the client requesting the token.</p><p>The client ID was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientId</code>. For backward compatibility, the <code>clientId</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.client.credentials.client.id</code> from conf [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.client.credentials.client.secret"></a><a id="connectconfigs_sasl.oauthbearer.client.credentials.client.secret" href="#connectconfigs_sasl.oauthbearer.client.credentials.client.secret">sasl.oauthbearer.client.credentials.client.secret</a></h4>
-<p><p>The secret (defined by either the user or preassigned, depending on the identity provider) of the client requesting the token.</p><p>The client secret was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientSecret</code>. For backward compatibility, the <code>clientSecret</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.cl [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.url"></a><a id="connectconfigs_sasl.oauthbearer.jwks.endpoint.url" href="#connectconfigs_sasl.oauthbearer.jwks.endpoint.url">sasl.oauthbearer.jwks.endpoint.url</a></h4>
-<p>The OAuth/OIDC provider URL from which the provider's <a href="https://datatracker.ietf.org/doc/html/rfc7517#section-5">JWKS (JSON Web Key Set)</a> can be retrieved. The URL can be HTTP(S)-based or file-based. If the URL is HTTP(S)-based, the JWKS data will be retrieved from the OAuth/OIDC provider via the configured URL on broker startup. All then-current keys will be cached on the broker for incoming requests. If an authentication request is received for a JWT that includes a "kid" [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwt.retriever.class"></a><a id="connectconfigs_sasl.oauthbearer.jwt.retriever.class" href="#connectconfigs_sasl.oauthbearer.jwt.retriever.class">sasl.oauthbearer.jwt.retriever.class</a></h4>
-<p><p>The fully-qualified class name of a <code>JwtRetriever</code> implementation used to request tokens from the identity provider.</p><p>The default configuration value represents a class that maintains backward compatibility with previous versions of Apache Kafka. The default implementation uses the configuration to determine which concrete implementation to create.<p>Other implementations that are provided include:</p><ul><li><code>org.apache.kafka.common.security.oauthbearer.Client [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtRetriever</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwt.validator.class"></a><a id="connectconfigs_sasl.oauthbearer.jwt.validator.class" href="#connectconfigs_sasl.oauthbearer.jwt.validator.class">sasl.oauthbearer.jwt.validator.class</a></h4>
-<p><p>The fully-qualified class name of a <code>JwtValidator</code> implementation used to validate the JWT from the identity provider.</p><p>The default validator (<code>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</code>) maintains backward compatibility with previous versions of Apache Kafka. The default validator uses configuration to determine which concrete implementation to create.<p>The built-in <code>JwtValidator</code> implementations are:</p><ul><li><code>o [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.scope"></a><a id="connectconfigs_sasl.oauthbearer.scope" href="#connectconfigs_sasl.oauthbearer.scope">sasl.oauthbearer.scope</a></h4>
-<p><p>This is the level of access a client application is granted to a resource or API which is included in the token request. If provided, it should match one or more scopes configured in the identity provider.</p><p>The scope was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>scope</code>. For backward compatibility, the <code>scope</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p> [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.token.endpoint.url"></a><a id="connectconfigs_sasl.oauthbearer.token.endpoint.url" href="#connectconfigs_sasl.oauthbearer.token.endpoint.url">sasl.oauthbearer.token.endpoint.url</a></h4>
-<p>The URL for the OAuth/OIDC identity provider. If the URL is HTTP(S)-based, it is the issuer's token endpoint URL to which requests will be made to login based on the configuration in <code>sasl.oauthbearer.jwt.retriever.class</code>. If the URL is file-based, it specifies a file containing an access token (in JWT serialized form) issued by the OAuth/OIDC identity provider to use for authorization.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="security.protocol"></a><a id="connectconfigs_security.protocol" href="#connectconfigs_security.protocol">security.protocol</a></h4>
-<p>Protocol used to communicate with brokers.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>PLAINTEXT</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [SASL_SSL, PLAINTEXT, SSL, SASL_PLAINTEXT]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="send.buffer.bytes"></a><a id="connectconfigs_send.buffer.bytes" href="#connectconfigs_send.buffer.bytes">send.buffer.bytes</a></h4>
-<p>The size of the TCP send buffer (SO_SNDBUF) to use when sending data. If the value is -1, the OS default will be used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>131072 (128 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.enabled.protocols"></a><a id="connectconfigs_ssl.enabled.protocols" href="#connectconfigs_ssl.enabled.protocols">ssl.enabled.protocols</a></h4>
-<p>The list of protocols enabled for SSL connections. The default is 'TLSv1.2,TLSv1.3'. This means that clients and servers will prefer TLSv1.3 if both support it and fallback to TLSv1.2 otherwise (assuming both support at least TLSv1.2). This default should be fine for most use cases. If this configuration is set to an empty list, Kafka will use the protocols enabled by default in the underlying SSLEngine, which may include additional protocols depending on the JVM version. Also see the [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>TLSv1.2,TLSv1.3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.type"></a><a id="connectconfigs_ssl.keystore.type" href="#connectconfigs_ssl.keystore.type">ssl.keystore.type</a></h4>
-<p>The file format of the key store file. This is optional for client. The values currently supported by the default <code>ssl.engine.factory.class</code> are [JKS, PKCS12, PEM].</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>JKS</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.protocol"></a><a id="connectconfigs_ssl.protocol" href="#connectconfigs_ssl.protocol">ssl.protocol</a></h4>
-<p>The SSL protocol used to generate the SSLContext. The default is 'TLSv1.3', which should be fine for most use cases. A typical alternative to the default is 'TLSv1.2'. Allowed values for this config are dependent on the JVM. Clients using the defaults for this config and 'ssl.enabled.protocols' will downgrade to 'TLSv1.2' if the server does not support 'TLSv1.3'. If this config is set to 'TLSv1.2', however, clients will not use 'TLSv1.3' even if it is one of the values in <code>ssl.en [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>TLSv1.3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.provider"></a><a id="connectconfigs_ssl.provider" href="#connectconfigs_ssl.provider">ssl.provider</a></h4>
-<p>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.type"></a><a id="connectconfigs_ssl.truststore.type" href="#connectconfigs_ssl.truststore.type">ssl.truststore.type</a></h4>
-<p>The file format of the trust store file. The values currently supported by the default <code>ssl.engine.factory.class</code> are [JKS, PKCS12, PEM].</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>JKS</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="worker.sync.timeout.ms"></a><a id="connectconfigs_worker.sync.timeout.ms" href="#connectconfigs_worker.sync.timeout.ms">worker.sync.timeout.ms</a></h4>
-<p>When the worker is out of sync with other workers and needs to resynchronize configurations, wait up to this amount of time before giving up, leaving the group, and waiting a backoff period before rejoining.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>3000 (3 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="worker.unsync.backoff.ms"></a><a id="connectconfigs_worker.unsync.backoff.ms" href="#connectconfigs_worker.unsync.backoff.ms">worker.unsync.backoff.ms</a></h4>
-<p>When the worker is out of sync with other workers and fails to catch up within the <code>worker.sync.timeout.ms</code>, leave the Connect cluster for this long before rejoining.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="access.control.allow.methods"></a><a id="connectconfigs_access.control.allow.methods" href="#connectconfigs_access.control.allow.methods">access.control.allow.methods</a></h4>
-<p>Sets the methods supported for cross origin requests by setting the Access-Control-Allow-Methods header. The default value of the Access-Control-Allow-Methods header allows cross origin requests for GET, POST and HEAD.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="access.control.allow.origin"></a><a id="connectconfigs_access.control.allow.origin" href="#connectconfigs_access.control.allow.origin">access.control.allow.origin</a></h4>
-<p>Value to set the Access-Control-Allow-Origin header to for REST API requests.To enable cross origin access, set this to the domain of the application that should be permitted to access the API, or '*' to allow access from any domain. The default value only allows access from the domain of the REST API.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="admin.listeners"></a><a id="connectconfigs_admin.listeners" href="#connectconfigs_admin.listeners">admin.listeners</a></h4>
-<p>List of comma-separated URIs the Admin REST API will listen on. The supported protocols are HTTP and HTTPS. An empty or blank string will disable this feature. The default behavior is to use the regular listener (specified by the 'listeners' property). A comma-separated list of valid URLs, e.g., http://localhost:8080,https://localhost:8443.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="client.id"></a><a id="connectconfigs_client.id" href="#connectconfigs_client.id">client.id</a></h4>
-<p>An id string to pass to the server when making requests. The purpose of this is to be able to track the source of requests beyond just ip/port by allowing a logical application name to be included in server-side request logging.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="config.providers"></a><a id="connectconfigs_config.providers" href="#connectconfigs_config.providers">config.providers</a></h4>
-<p>Comma-separated alias names for classes implementing the <code>ConfigProvider</code> interface. This enables loading configuration data (such as passwords, API keys, and other credentials) from external sources. For example, see <a href="https://kafka.apache.org/documentation/#config_providers">Configuration Providers</a>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="config.storage.replication.factor"></a><a id="connectconfigs_config.storage.replication.factor" href="#connectconfigs_config.storage.replication.factor">config.storage.replication.factor</a></h4>
-<p>Replication factor used when creating the configuration storage topic</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td>Positive number not larger than the number of brokers in the Kafka cluster, or -1 to use the broker's default</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="connect.protocol"></a><a id="connectconfigs_connect.protocol" href="#connectconfigs_connect.protocol">connect.protocol</a></h4>
-<p>Compatibility mode for Kafka Connect Protocol</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>sessioned</td></tr>
-<tr><th>Valid Values:</th><td>[eager, compatible, sessioned]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="header.converter"></a><a id="connectconfigs_header.converter" href="#connectconfigs_header.converter">header.converter</a></h4>
-<p>HeaderConverter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the header values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro. By default, the SimpleHeaderConverter is used to serialize header values to strings and deserialize them by inferring the sche [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.connect.storage.SimpleHeaderConverter</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="header.converter.plugin.version"></a><a id="connectconfigs_header.converter.plugin.version" href="#connectconfigs_header.converter.plugin.version">header.converter.plugin.version</a></h4>
-<p>Version of the header converter.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="inter.worker.key.generation.algorithm"></a><a id="connectconfigs_inter.worker.key.generation.algorithm" href="#connectconfigs_inter.worker.key.generation.algorithm">inter.worker.key.generation.algorithm</a></h4>
-<p>The algorithm to use for generating internal request keys. The algorithm 'HmacSHA256' will be used as a default on JVMs that support it; on other JVMs, no default is used and a value for this property must be manually specified in the worker config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>HmacSHA256</td></tr>
-<tr><th>Valid Values:</th><td>Any KeyGenerator algorithm supported by the worker JVM</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="inter.worker.key.size"></a><a id="connectconfigs_inter.worker.key.size" href="#connectconfigs_inter.worker.key.size">inter.worker.key.size</a></h4>
-<p>The size of the key to use for signing internal requests, in bits. If null, the default key size for the key generation algorithm will be used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="inter.worker.key.ttl.ms"></a><a id="connectconfigs_inter.worker.key.ttl.ms" href="#connectconfigs_inter.worker.key.ttl.ms">inter.worker.key.ttl.ms</a></h4>
-<p>The TTL of generated session keys used for internal request validation (in milliseconds)</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,2147483647]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="inter.worker.signature.algorithm"></a><a id="connectconfigs_inter.worker.signature.algorithm" href="#connectconfigs_inter.worker.signature.algorithm">inter.worker.signature.algorithm</a></h4>
-<p>The algorithm used to sign internal requests. The algorithm 'HmacSHA256' will be used as a default on JVMs that support it; on other JVMs, no default is used and a value for this property must be manually specified in the worker config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>HmacSHA256</td></tr>
-<tr><th>Valid Values:</th><td>Any MAC algorithm supported by the worker JVM</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="inter.worker.verification.algorithms"></a><a id="connectconfigs_inter.worker.verification.algorithms" href="#connectconfigs_inter.worker.verification.algorithms">inter.worker.verification.algorithms</a></h4>
-<p>A list of permitted algorithms for verifying internal requests, which must include the algorithm used for the <code>inter.worker.signature.algorithm</code> property. The algorithm(s) '[HmacSHA256]' will be used as a default on JVMs that provide them; on other JVMs, no default is used and a value for this property must be manually specified in the worker config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>HmacSHA256</td></tr>
-<tr><th>Valid Values:</th><td>A list of one or more MAC algorithms, each supported by the worker JVM</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="key.converter.plugin.version"></a><a id="connectconfigs_key.converter.plugin.version" href="#connectconfigs_key.converter.plugin.version">key.converter.plugin.version</a></h4>
-<p>Version of the key converter.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="listeners"></a><a id="connectconfigs_listeners" href="#connectconfigs_listeners">listeners</a></h4>
-<p>List of comma-separated URIs the REST API will listen on. The supported protocols are HTTP and HTTPS.<br> Specify hostname as 0.0.0.0 to bind to all interfaces.<br> Leave hostname empty to bind to default interface.<br> Examples of legal listener lists: HTTP://myhost:8083,HTTPS://myhost:8084</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>http://:8083</td></tr>
-<tr><th>Valid Values:</th><td>List of comma-separated URLs, ex: http://localhost:8080,https://localhost:8443.</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.max.age.ms"></a><a id="connectconfigs_metadata.max.age.ms" href="#connectconfigs_metadata.max.age.ms">metadata.max.age.ms</a></h4>
-<p>The period of time in milliseconds after which we force a refresh of metadata even if we haven't seen any partition leadership changes to proactively discover any new brokers or partitions.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.recovery.rebootstrap.trigger.ms"></a><a id="connectconfigs_metadata.recovery.rebootstrap.trigger.ms" href="#connectconfigs_metadata.recovery.rebootstrap.trigger.ms">metadata.recovery.rebootstrap.trigger.ms</a></h4>
-<p>If a client configured to rebootstrap using <code>metadata.recovery.strategy=rebootstrap</code> is unable to obtain metadata from any of the brokers in the last known metadata for this interval, client repeats the bootstrap process using <code>bootstrap.servers</code> configuration.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.recovery.strategy"></a><a id="connectconfigs_metadata.recovery.strategy" href="#connectconfigs_metadata.recovery.strategy">metadata.recovery.strategy</a></h4>
-<p>Controls how the client recovers when none of the brokers known to it is available. If set to <code>none</code>, the client fails. If set to <code>rebootstrap</code>, the client repeats the bootstrap process using <code>bootstrap.servers</code>. Rebootstrapping is useful when a client communicates with brokers so infrequently that the set of brokers may change entirely before the client refreshes metadata. Metadata recovery is triggered when all last-known brokers appear unavailable s [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>rebootstrap</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [REBOOTSTRAP, NONE]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metric.reporters"></a><a id="connectconfigs_metric.reporters" href="#connectconfigs_metric.reporters">metric.reporters</a></h4>
-<p>A list of classes to use as metrics reporters. Implementing the <code>org.apache.kafka.common.metrics.MetricsReporter</code> interface allows plugging in classes that will be notified of new metric creation. When custom reporters are set and <code>org.apache.kafka.common.metrics.JmxReporter</code> is needed, it has to be explicitly added to the list.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.metrics.JmxReporter</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.num.samples"></a><a id="connectconfigs_metrics.num.samples" href="#connectconfigs_metrics.num.samples">metrics.num.samples</a></h4>
-<p>The number of samples maintained to compute metrics.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.recording.level"></a><a id="connectconfigs_metrics.recording.level" href="#connectconfigs_metrics.recording.level">metrics.recording.level</a></h4>
-<p>The highest recording level for metrics. It has three levels for recording metrics - info, debug, and trace.<br> <br>INFO level records only essential metrics necessary for monitoring system performance and health. It collects vital data without gathering too much detail, making it suitable for production environments where minimal overhead is desired.<br><br>DEBUG level records most metrics, providing more detailed information about the system's operation. It's useful for development [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>INFO</td></tr>
-<tr><th>Valid Values:</th><td>[INFO, DEBUG]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.sample.window.ms"></a><a id="connectconfigs_metrics.sample.window.ms" href="#connectconfigs_metrics.sample.window.ms">metrics.sample.window.ms</a></h4>
-<p>The window of time a metrics sample is computed over.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offset.flush.interval.ms"></a><a id="connectconfigs_offset.flush.interval.ms" href="#connectconfigs_offset.flush.interval.ms">offset.flush.interval.ms</a></h4>
-<p>Interval at which to try committing offsets for tasks.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offset.flush.timeout.ms"></a><a id="connectconfigs_offset.flush.timeout.ms" href="#connectconfigs_offset.flush.timeout.ms">offset.flush.timeout.ms</a></h4>
-<p>Maximum number of milliseconds to wait for records to flush and partition offset data to be committed to offset storage before cancelling the process and restoring the offset data to be committed in a future attempt. This property has no effect for source connectors running with exactly-once support.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offset.storage.partitions"></a><a id="connectconfigs_offset.storage.partitions" href="#connectconfigs_offset.storage.partitions">offset.storage.partitions</a></h4>
-<p>The number of partitions used when creating the offset storage topic</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>25</td></tr>
-<tr><th>Valid Values:</th><td>Positive number, or -1 to use the broker's default</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offset.storage.replication.factor"></a><a id="connectconfigs_offset.storage.replication.factor" href="#connectconfigs_offset.storage.replication.factor">offset.storage.replication.factor</a></h4>
-<p>Replication factor used when creating the offset storage topic</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td>Positive number not larger than the number of brokers in the Kafka cluster, or -1 to use the broker's default</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="plugin.discovery"></a><a id="connectconfigs_plugin.discovery" href="#connectconfigs_plugin.discovery">plugin.discovery</a></h4>
-<p>Method to use to discover plugins present in the classpath and plugin.path configuration. This can be one of multiple values with the following meanings:<br>* only_scan: Discover plugins only by reflection. Plugins which are not discoverable by ServiceLoader will not impact worker startup.<br>* hybrid_warn: Discover plugins reflectively and by ServiceLoader. Plugins which are not discoverable by ServiceLoader will print warnings during worker startup.<br>* hybrid_fail: Discover plugin [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>hybrid_warn</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [ONLY_SCAN, SERVICE_LOAD, HYBRID_WARN, HYBRID_FAIL]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="plugin.path"></a><a id="connectconfigs_plugin.path" href="#connectconfigs_plugin.path">plugin.path</a></h4>
-<p>List of paths separated by commas (,) that contain plugins (connectors, converters, transformations). The list should consist of top level directories that include any combination of: <br>a) directories immediately containing jars with plugins and their dependencies<br>b) uber-jars with plugins and their dependencies<br>c) directories immediately containing the package directory structure of classes of plugins and their dependencies<br>Note: symlinks will be followed to discover depen [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="reconnect.backoff.max.ms"></a><a id="connectconfigs_reconnect.backoff.max.ms" href="#connectconfigs_reconnect.backoff.max.ms">reconnect.backoff.max.ms</a></h4>
-<p>The maximum amount of time in milliseconds to wait when reconnecting to a broker that has repeatedly failed to connect. If provided, the backoff per host will increase exponentially for each consecutive connection failure, up to this maximum. After calculating the backoff increase, 20% random jitter is added to avoid connection storms.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="reconnect.backoff.ms"></a><a id="connectconfigs_reconnect.backoff.ms" href="#connectconfigs_reconnect.backoff.ms">reconnect.backoff.ms</a></h4>
-<p>The base amount of time to wait before attempting to reconnect to a given host. This avoids repeatedly connecting to a host in a tight loop. This backoff applies to all connection attempts by the client to a broker. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>reconnect.backoff.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>50</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="response.http.headers.config"></a><a id="connectconfigs_response.http.headers.config" href="#connectconfigs_response.http.headers.config">response.http.headers.config</a></h4>
-<p>Rules for REST API HTTP response headers</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td>Comma-separated header rules, where each header rule is of the form '[action] [header name]:[header value]' and optionally surrounded by double quotes if any part of a header rule contains a comma</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="rest.advertised.host.name"></a><a id="connectconfigs_rest.advertised.host.name" href="#connectconfigs_rest.advertised.host.name">rest.advertised.host.name</a></h4>
-<p>If this is set, this is the hostname that will be given out to other workers to connect to.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="rest.advertised.listener"></a><a id="connectconfigs_rest.advertised.listener" href="#connectconfigs_rest.advertised.listener">rest.advertised.listener</a></h4>
-<p>Sets the advertised listener (HTTP or HTTPS) which will be given to other workers to use.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="rest.advertised.port"></a><a id="connectconfigs_rest.advertised.port" href="#connectconfigs_rest.advertised.port">rest.advertised.port</a></h4>
-<p>If this is set, this is the port that will be given out to other workers to connect to.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="rest.extension.classes"></a><a id="connectconfigs_rest.extension.classes" href="#connectconfigs_rest.extension.classes">rest.extension.classes</a></h4>
-<p>Comma-separated names of <code>ConnectRestExtension</code> classes, loaded and called in the order specified. Implementing the interface <code>ConnectRestExtension</code> allows you to inject into Connect's REST API user defined resources like filters. Typically used to add custom capability like logging, security, etc. </p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="retry.backoff.max.ms"></a><a id="connectconfigs_retry.backoff.max.ms" href="#connectconfigs_retry.backoff.max.ms">retry.backoff.max.ms</a></h4>
-<p>The maximum amount of time in milliseconds to wait when retrying a request to the broker that has repeatedly failed. If provided, the backoff per client will increase exponentially for each failed request, up to this maximum. To prevent all clients from being synchronized upon retry, a randomized jitter with a factor of 0.2 will be applied to the backoff, resulting in the backoff falling within a range between 20% below and 20% above the computed value. If <code>retry.backoff.ms</code [...]
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="retry.backoff.ms"></a><a id="connectconfigs_retry.backoff.ms" href="#connectconfigs_retry.backoff.ms">retry.backoff.ms</a></h4>
-<p>The amount of time to wait before attempting to retry a failed request to a given topic partition. This avoids repeatedly sending requests in a tight loop under some failure scenarios. This value is the initial backoff value and will increase exponentially for each failed request, up to the <code>retry.backoff.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.kinit.cmd"></a><a id="connectconfigs_sasl.kerberos.kinit.cmd" href="#connectconfigs_sasl.kerberos.kinit.cmd">sasl.kerberos.kinit.cmd</a></h4>
-<p>Kerberos kinit command path.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>/usr/bin/kinit</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.min.time.before.relogin"></a><a id="connectconfigs_sasl.kerberos.min.time.before.relogin" href="#connectconfigs_sasl.kerberos.min.time.before.relogin">sasl.kerberos.min.time.before.relogin</a></h4>
-<p>Login thread sleep time between refresh attempts.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60000</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.ticket.renew.jitter"></a><a id="connectconfigs_sasl.kerberos.ticket.renew.jitter" href="#connectconfigs_sasl.kerberos.ticket.renew.jitter">sasl.kerberos.ticket.renew.jitter</a></h4>
-<p>Percentage of random jitter added to the renewal time.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.05</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.ticket.renew.window.factor"></a><a id="connectconfigs_sasl.kerberos.ticket.renew.window.factor" href="#connectconfigs_sasl.kerberos.ticket.renew.window.factor">sasl.kerberos.ticket.renew.window.factor</a></h4>
-<p>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.8</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.connect.timeout.ms"></a><a id="connectconfigs_sasl.login.connect.timeout.ms" href="#connectconfigs_sasl.login.connect.timeout.ms">sasl.login.connect.timeout.ms</a></h4>
-<p>The (optional) value in milliseconds for the external authentication provider connection timeout. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.read.timeout.ms"></a><a id="connectconfigs_sasl.login.read.timeout.ms" href="#connectconfigs_sasl.login.read.timeout.ms">sasl.login.read.timeout.ms</a></h4>
-<p>The (optional) value in milliseconds for the external authentication provider read timeout. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.buffer.seconds"></a><a id="connectconfigs_sasl.login.refresh.buffer.seconds" href="#connectconfigs_sasl.login.refresh.buffer.seconds">sasl.login.refresh.buffer.seconds</a></h4>
-<p>The amount of buffer time before credential expiration to maintain when refreshing a credential, in seconds. If a refresh would otherwise occur closer to expiration than the number of buffer seconds then the refresh will be moved up to maintain as much of the buffer time as possible. Legal values are between 0 and 3600 (1 hour); a default value of 300 (5 minutes) is used if no value is specified. This value and sasl.login.refresh.min.period.seconds are both ignored if their sum excee [...]
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.min.period.seconds"></a><a id="connectconfigs_sasl.login.refresh.min.period.seconds" href="#connectconfigs_sasl.login.refresh.min.period.seconds">sasl.login.refresh.min.period.seconds</a></h4>
-<p>The desired minimum time for the login refresh thread to wait before refreshing a credential, in seconds. Legal values are between 0 and 900 (15 minutes); a default value of 60 (1 minute) is used if no value is specified. This value and sasl.login.refresh.buffer.seconds are both ignored if their sum exceeds the remaining lifetime of a credential. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,900]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.window.factor"></a><a id="connectconfigs_sasl.login.refresh.window.factor" href="#connectconfigs_sasl.login.refresh.window.factor">sasl.login.refresh.window.factor</a></h4>
-<p>Login refresh thread will sleep until the specified window factor relative to the credential's lifetime has been reached, at which time it will try to refresh the credential. Legal values are between 0.5 (50%) and 1.0 (100%) inclusive; a default value of 0.8 (80%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.8</td></tr>
-<tr><th>Valid Values:</th><td>[0.5,...,1.0]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.window.jitter"></a><a id="connectconfigs_sasl.login.refresh.window.jitter" href="#connectconfigs_sasl.login.refresh.window.jitter">sasl.login.refresh.window.jitter</a></h4>
-<p>The maximum amount of random jitter relative to the credential's lifetime that is added to the login refresh thread's sleep time. Legal values are between 0 and 0.25 (25%) inclusive; a default value of 0.05 (5%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.05</td></tr>
-<tr><th>Valid Values:</th><td>[0.0,...,0.25]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.retry.backoff.max.ms"></a><a id="connectconfigs_sasl.login.retry.backoff.max.ms" href="#connectconfigs_sasl.login.retry.backoff.max.ms">sasl.login.retry.backoff.max.ms</a></h4>
-<p>The (optional) value in milliseconds for the maximum wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.retry.backoff.ms"></a><a id="connectconfigs_sasl.login.retry.backoff.ms" href="#connectconfigs_sasl.login.retry.backoff.ms">sasl.login.retry.backoff.ms</a></h4>
-<p>The (optional) value in milliseconds for the initial wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.exp.seconds"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.exp.seconds" href="#connectconfigs_sasl.oauthbearer.assertion.claim.exp.seconds">sasl.oauthbearer.assertion.claim.exp.seconds</a></h4>
-<p><p>The number of seconds <em>in the future</em> for which the JWT is valid. The value is used to determine the JWT <code>exp</code> (Expiration) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>exp</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> exp = x + y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbear [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,86400]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.nbf.seconds"></a><a id="connectconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds" href="#connectconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds">sasl.oauthbearer.assertion.claim.nbf.seconds</a></h4>
-<p><p>The number of seconds <em>in the past</em> from which the JWT is valid. The value is used to determine the JWT <code>nbf</code> (Not Before) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>nbf</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> nbf = x - y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbeare [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.clock.skew.seconds"></a><a id="connectconfigs_sasl.oauthbearer.clock.skew.seconds" href="#connectconfigs_sasl.oauthbearer.clock.skew.seconds">sasl.oauthbearer.clock.skew.seconds</a></h4>
-<p>The (optional) value in seconds to allow for differences between the time of the OAuth/OIDC identity provider and the broker.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.expected.audience"></a><a id="connectconfigs_sasl.oauthbearer.expected.audience" href="#connectconfigs_sasl.oauthbearer.expected.audience">sasl.oauthbearer.expected.audience</a></h4>
-<p>The (optional) comma-delimited setting for the broker to use to verify that the JWT was issued for one of the expected audiences. The JWT will be inspected for the standard OAuth "aud" claim and if this value is set, the broker will match the value from JWT's "aud" claim to see if there is an exact match. If there is no match, the broker will reject the JWT and authentication will fail.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.expected.issuer"></a><a id="connectconfigs_sasl.oauthbearer.expected.issuer" href="#connectconfigs_sasl.oauthbearer.expected.issuer">sasl.oauthbearer.expected.issuer</a></h4>
-<p>The (optional) setting for the broker to use to verify that the JWT was created by the expected issuer. The JWT will be inspected for the standard OAuth "iss" claim and if this value is set, the broker will match it exactly against what is in the JWT's "iss" claim. If there is no match, the broker will reject the JWT and authentication will fail.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.header.urlencode"></a><a id="connectconfigs_sasl.oauthbearer.header.urlencode" href="#connectconfigs_sasl.oauthbearer.header.urlencode">sasl.oauthbearer.header.urlencode</a></h4>
-<p>The (optional) setting to enable the OAuth client to URL-encode the client_id and client_secret in the authorization header in accordance with RFC6749, see <a href="https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1">here</a> for more details. The default value is set to 'false' for backward compatibility</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.refresh.ms"></a><a id="connectconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms" href="#connectconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms">sasl.oauthbearer.jwks.endpoint.refresh.ms</a></h4>
-<p>The (optional) value in milliseconds for the broker to wait between refreshing its JWKS (JSON Web Key Set) cache that contains the keys to verify the signature of the JWT.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms"></a><a id="connectconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms" href="#connectconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms</a></h4>
-<p>The (optional) value in milliseconds for the maximum wait between attempts to retrieve the JWKS (JSON Web Key Set) from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.ms"></a><a id="connectconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms" href="#connectconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.ms</a></h4>
-<p>The (optional) value in milliseconds for the initial wait between JWKS (JSON Web Key Set) retrieval attempts from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.scope.claim.name"></a><a id="connectconfigs_sasl.oauthbearer.scope.claim.name" href="#connectconfigs_sasl.oauthbearer.scope.claim.name">sasl.oauthbearer.scope.claim.name</a></h4>
-<p>The OAuth claim for the scope is often named "scope", but this (optional) setting can provide a different name to use for the scope included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>scope</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.sub.claim.name"></a><a id="connectconfigs_sasl.oauthbearer.sub.claim.name" href="#connectconfigs_sasl.oauthbearer.sub.claim.name">sasl.oauthbearer.sub.claim.name</a></h4>
-<p>The OAuth claim for the subject is often named "sub", but this (optional) setting can provide a different name to use for the subject included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>sub</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="scheduled.rebalance.max.delay.ms"></a><a id="connectconfigs_scheduled.rebalance.max.delay.ms" href="#connectconfigs_scheduled.rebalance.max.delay.ms">scheduled.rebalance.max.delay.ms</a></h4>
-<p>The maximum delay that is scheduled in order to wait for the return of one or more departed workers before rebalancing and reassigning their connectors and tasks to the group. During this period the connectors and tasks of the departed workers remain unassigned</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,2147483647]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.connection.setup.timeout.max.ms"></a><a id="connectconfigs_socket.connection.setup.timeout.max.ms" href="#connectconfigs_socket.connection.setup.timeout.max.ms">socket.connection.setup.timeout.max.ms</a></h4>
-<p>The maximum amount of time the client will wait for the socket connection to be established. The connection setup timeout will increase exponentially for each consecutive connection failure up to this maximum. To avoid connection storms, a randomization factor of 0.2 will be applied to the timeout resulting in a random range between 20% below and 20% above the computed value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.connection.setup.timeout.ms"></a><a id="connectconfigs_socket.connection.setup.timeout.ms" href="#connectconfigs_socket.connection.setup.timeout.ms">socket.connection.setup.timeout.ms</a></h4>
-<p>The amount of time the client will wait for the socket connection to be established. If the connection is not built before the timeout elapses, clients will close the socket channel. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>socket.connection.setup.timeout.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.cipher.suites"></a><a id="connectconfigs_ssl.cipher.suites" href="#connectconfigs_ssl.cipher.suites">ssl.cipher.suites</a></h4>
-<p>A list of cipher suites. This is a named combination of authentication, encryption, MAC and key exchange algorithm used to negotiate the security settings for a network connection using TLS or SSL network protocol. By default all the available cipher suites are supported.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.client.auth"></a><a id="connectconfigs_ssl.client.auth" href="#connectconfigs_ssl.client.auth">ssl.client.auth</a></h4>
-<p>Configures kafka broker to request client authentication. The following settings are common: <ul> <li><code>ssl.client.auth=required</code> If set to required client authentication is required. <li><code>ssl.client.auth=requested</code> This means client authentication is optional. unlike required, if this option is set client can choose not to provide authentication information about itself <li><code>ssl.client.auth=none</code> This means client authentication is not needed.</ul></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>none</td></tr>
-<tr><th>Valid Values:</th><td>[required, requested, none]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.endpoint.identification.algorithm"></a><a id="connectconfigs_ssl.endpoint.identification.algorithm" href="#connectconfigs_ssl.endpoint.identification.algorithm">ssl.endpoint.identification.algorithm</a></h4>
-<p>The endpoint identification algorithm to validate server hostname using server certificate. </p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>https</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.engine.factory.class"></a><a id="connectconfigs_ssl.engine.factory.class" href="#connectconfigs_ssl.engine.factory.class">ssl.engine.factory.class</a></h4>
-<p>The class of type org.apache.kafka.common.security.auth.SslEngineFactory to provide SSLEngine objects. Default value is org.apache.kafka.common.security.ssl.DefaultSslEngineFactory. Alternatively, setting this to org.apache.kafka.common.security.ssl.CommonNameLoggingSslEngineFactory will log the common name of expired SSL certificates used by clients to authenticate at any of the brokers with log level INFO. Note that this will cause a tiny delay during establishment of new connection [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keymanager.algorithm"></a><a id="connectconfigs_ssl.keymanager.algorithm" href="#connectconfigs_ssl.keymanager.algorithm">ssl.keymanager.algorithm</a></h4>
-<p>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>SunX509</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.secure.random.implementation"></a><a id="connectconfigs_ssl.secure.random.implementation" href="#connectconfigs_ssl.secure.random.implementation">ssl.secure.random.implementation</a></h4>
-<p>The SecureRandom PRNG implementation to use for SSL cryptography operations. </p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.trustmanager.algorithm"></a><a id="connectconfigs_ssl.trustmanager.algorithm" href="#connectconfigs_ssl.trustmanager.algorithm">ssl.trustmanager.algorithm</a></h4>
-<p>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>PKIX</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="status.storage.partitions"></a><a id="connectconfigs_status.storage.partitions" href="#connectconfigs_status.storage.partitions">status.storage.partitions</a></h4>
-<p>The number of partitions used when creating the status storage topic</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5</td></tr>
-<tr><th>Valid Values:</th><td>Positive number, or -1 to use the broker's default</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="status.storage.replication.factor"></a><a id="connectconfigs_status.storage.replication.factor" href="#connectconfigs_status.storage.replication.factor">status.storage.replication.factor</a></h4>
-<p>Replication factor used when creating the status storage topic</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td>Positive number not larger than the number of brokers in the Kafka cluster, or -1 to use the broker's default</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="task.shutdown.graceful.timeout.ms"></a><a id="connectconfigs_task.shutdown.graceful.timeout.ms" href="#connectconfigs_task.shutdown.graceful.timeout.ms">task.shutdown.graceful.timeout.ms</a></h4>
-<p>Amount of time to wait for tasks to shutdown gracefully. This is the total amount of time, not per task. All task have shutdown triggered, then they are waited on sequentially.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="topic.creation.enable"></a><a id="connectconfigs_topic.creation.enable" href="#connectconfigs_topic.creation.enable">topic.creation.enable</a></h4>
-<p>Whether to allow automatic creation of topics used by source connectors, when source connectors are configured with <code>topic.creation.</code> properties. Each task will use an admin client to create its topics and will not depend on the Kafka brokers to create topics automatically.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="topic.tracking.allow.reset"></a><a id="connectconfigs_topic.tracking.allow.reset" href="#connectconfigs_topic.tracking.allow.reset">topic.tracking.allow.reset</a></h4>
-<p>If set to true, it allows user requests to reset the set of active topics per connector.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="topic.tracking.enable"></a><a id="connectconfigs_topic.tracking.enable" href="#connectconfigs_topic.tracking.enable">topic.tracking.enable</a></h4>
-<p>Enable tracking the set of active topics per connector during runtime.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="value.converter.plugin.version"></a><a id="connectconfigs_value.converter.plugin.version" href="#connectconfigs_value.converter.plugin.version">value.converter.plugin.version</a></h4>
-<p>Version of the value converter.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-</ul>
-
diff --git a/content/en/43/generated/connect_metrics.html b/content/en/43/generated/connect_metrics.html
index d0e0f045db..e69de29bb2 100644
--- a/content/en/43/generated/connect_metrics.html
+++ b/content/en/43/generated/connect_metrics.html
@@ -1,463 +0,0 @@
-<table class="data-table">
-<tbody>
-<tr>
-<th>Metric/Attribute name</th>
-<th>Description</th>
-<th>Mbean name</th>
-</tr>
-<tr>
-<td>connector-count</td>
-<td>The number of connectors run in this worker.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>connector-startup-attempts-total</td>
-<td>The total number of connector startups that this worker has attempted.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>connector-startup-failure-percentage</td>
-<td>The average percentage of this worker's connectors starts that failed.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>connector-startup-failure-total</td>
-<td>The total number of connector starts that failed.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>connector-startup-success-percentage</td>
-<td>The average percentage of this worker's connectors starts that succeeded.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>connector-startup-success-total</td>
-<td>The total number of connector starts that succeeded.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>task-count</td>
-<td>The number of tasks run in this worker.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>task-startup-attempts-total</td>
-<td>The total number of task startups that this worker has attempted.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>task-startup-failure-percentage</td>
-<td>The average percentage of this worker's tasks starts that failed.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>task-startup-failure-total</td>
-<td>The total number of task starts that failed.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>task-startup-success-percentage</td>
-<td>The average percentage of this worker's tasks starts that succeeded.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>task-startup-success-total</td>
-<td>The total number of task starts that succeeded.</td>
-<td>kafka.connect:type=connect-worker-metrics</td>
-</tr>
-<tr>
-<td>connector-destroyed-task-count</td>
-<td>The number of destroyed tasks of the connector on the worker.</td>
-<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>connector-failed-task-count</td>
-<td>The number of failed tasks of the connector on the worker.</td>
-<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>connector-paused-task-count</td>
-<td>The number of paused tasks of the connector on the worker.</td>
-<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>connector-restarting-task-count</td>
-<td>The number of restarting tasks of the connector on the worker.</td>
-<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>connector-running-task-count</td>
-<td>The number of running tasks of the connector on the worker.</td>
-<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>connector-total-task-count</td>
-<td>The number of tasks of the connector on the worker.</td>
-<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>connector-unassigned-task-count</td>
-<td>The number of unassigned tasks of the connector on the worker.</td>
-<td>kafka.connect:type=connect-worker-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>completed-rebalances-total</td>
-<td>The total number of rebalances completed by this worker.</td>
-<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
-</tr>
-<tr>
-<td>connect-protocol</td>
-<td>The Connect protocol used by this cluster</td>
-<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
-</tr>
-<tr>
-<td>epoch</td>
-<td>The epoch or generation number of this worker.</td>
-<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
-</tr>
-<tr>
-<td>leader-name</td>
-<td>The name of the group leader.</td>
-<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
-</tr>
-<tr>
-<td>rebalance-avg-time-ms</td>
-<td>The average time in milliseconds spent by this worker to rebalance.</td>
-<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
-</tr>
-<tr>
-<td>rebalance-max-time-ms</td>
-<td>The maximum time in milliseconds spent by this worker to rebalance.</td>
-<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
-</tr>
-<tr>
-<td>rebalancing</td>
-<td>Whether this worker is currently rebalancing.</td>
-<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
-</tr>
-<tr>
-<td>time-since-last-rebalance-ms</td>
-<td>The time in milliseconds since this worker completed the most recent rebalance.</td>
-<td>kafka.connect:type=connect-worker-rebalance-metrics</td>
-</tr>
-<tr>
-<td>connector-class</td>
-<td>The name of the connector class.</td>
-<td>kafka.connect:type=connector-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>connector-type</td>
-<td>The type of the connector. One of 'source' or 'sink'.</td>
-<td>kafka.connect:type=connector-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>connector-version</td>
-<td>The version of the connector class, as reported by the connector.</td>
-<td>kafka.connect:type=connector-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>status</td>
-<td>The status of the connector. One of 'unassigned', 'running', 'paused', 'stopped', 'failed', or 'restarting'.</td>
-<td>kafka.connect:type=connector-metrics,connector="{connector}"</td>
-</tr>
-<tr>
-<td>predicate-class</td>
-<td>The class name of the predicate class</td>
-<td>kafka.connect:type=connector-predicate-metrics,connector="{connector}",task="{task}",predicate="{predicate}"</td>
-</tr>
-<tr>
-<td>predicate-version</td>
-<td>The version of the predicate class</td>
-<td>kafka.connect:type=connector-predicate-metrics,connector="{connector}",task="{task}",predicate="{predicate}"</td>
-</tr>
-<tr>
-<td>batch-size-avg</td>
-<td>The average number of records in the batches the task has processed so far.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>batch-size-max</td>
-<td>The number of records in the largest batch the task has processed so far.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>connector-class</td>
-<td>The name of the connector class.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>connector-type</td>
-<td>The type of the connector. One of 'source' or 'sink'.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>connector-version</td>
-<td>The version of the connector class, as reported by the connector.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>header-converter-class</td>
-<td>The fully qualified class name from header.converter</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>header-converter-version</td>
-<td>The version instantiated for header.converter. May be undefined</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>key-converter-class</td>
-<td>The fully qualified class name from key.converter</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>key-converter-version</td>
-<td>The version instantiated for key.converter. May be undefined</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>offset-commit-avg-time-ms</td>
-<td>The average time in milliseconds taken by this task to commit offsets.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>offset-commit-failure-percentage</td>
-<td>The average percentage of this task's offset commit attempts that failed.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>offset-commit-max-time-ms</td>
-<td>The maximum time in milliseconds taken by this task to commit offsets.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>offset-commit-success-percentage</td>
-<td>The average percentage of this task's offset commit attempts that succeeded.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>pause-ratio</td>
-<td>The fraction of time this task has spent in the pause state.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>running-ratio</td>
-<td>The fraction of time this task has spent in the running state.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>status</td>
-<td>The status of the connector task. One of 'unassigned', 'running', 'paused', 'failed', or 'restarting'.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>task-class</td>
-<td>The class name of the task.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>task-version</td>
-<td>The version of the task.</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>value-converter-class</td>
-<td>The fully qualified class name from value.converter</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>value-converter-version</td>
-<td>The version instantiated for value.converter. May be undefined</td>
-<td>kafka.connect:type=connector-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>transform-class</td>
-<td>The class name of the transformation class</td>
-<td>kafka.connect:type=connector-transform-metrics,connector="{connector}",task="{task}",transform="{transform}"</td>
-</tr>
-<tr>
-<td>transform-version</td>
-<td>The version of the transformation class</td>
-<td>kafka.connect:type=connector-transform-metrics,connector="{connector}",task="{task}",transform="{transform}"</td>
-</tr>
-<tr>
-<td>offset-commit-completion-rate</td>
-<td>The average per-second number of offset commit completions that were completed successfully.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>offset-commit-completion-total</td>
-<td>The total number of offset commit completions that were completed successfully.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>offset-commit-seq-no</td>
-<td>The current sequence number for offset commits.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>offset-commit-skip-rate</td>
-<td>The average per-second number of offset commit completions that were received too late and skipped/ignored.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>offset-commit-skip-total</td>
-<td>The total number of offset commit completions that were received too late and skipped/ignored.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>partition-count</td>
-<td>The number of topic partitions assigned to this task belonging to the named sink connector in this worker.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>put-batch-avg-time-ms</td>
-<td>The average time taken by this task to put a batch of sinks records.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>put-batch-max-time-ms</td>
-<td>The maximum time taken by this task to put a batch of sinks records.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>sink-record-active-count</td>
-<td>The number of records that have been read from Kafka but not yet completely committed/flushed/acknowledged by the sink task.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>sink-record-active-count-avg</td>
-<td>The average number of records that have been read from Kafka but not yet completely committed/flushed/acknowledged by the sink task.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>sink-record-active-count-max</td>
-<td>The maximum number of records that have been read from Kafka but not yet completely committed/flushed/acknowledged by the sink task.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>sink-record-lag-max</td>
-<td>The maximum lag in terms of number of records that the sink task is behind the consumer's position for any topic partitions.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>sink-record-read-rate</td>
-<td>The average per-second number of records read from Kafka for this task belonging to the named sink connector in this worker. This is before transformations are applied.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>sink-record-read-total</td>
-<td>The total number of records read from Kafka by this task belonging to the named sink connector in this worker, since the task was last restarted.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>sink-record-send-rate</td>
-<td>The average per-second number of records output from the transformations and sent/put to this task belonging to the named sink connector in this worker. This is after transformations are applied and excludes any records filtered out by the transformations.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>sink-record-send-total</td>
-<td>The total number of records output from the transformations and sent/put to this task belonging to the named sink connector in this worker, since the task was last restarted.</td>
-<td>kafka.connect:type=sink-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>poll-batch-avg-time-ms</td>
-<td>The average time in milliseconds taken by this task to poll for a batch of source records.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>poll-batch-max-time-ms</td>
-<td>The maximum time in milliseconds taken by this task to poll for a batch of source records.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>source-record-active-count</td>
-<td>The number of records that have been produced by this task but not yet completely written to Kafka.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>source-record-active-count-avg</td>
-<td>The average number of records that have been produced by this task but not yet completely written to Kafka.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>source-record-active-count-max</td>
-<td>The maximum number of records that have been produced by this task but not yet completely written to Kafka.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>source-record-poll-rate</td>
-<td>The average per-second number of records produced/polled (before transformation) by this task belonging to the named source connector in this worker.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>source-record-poll-total</td>
-<td>The total number of records produced/polled (before transformation) by this task belonging to the named source connector in this worker.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>source-record-write-rate</td>
-<td>The average per-second number of records written to Kafka for this task belonging to the named source connector in this worker, since the task was last restarted. This is after transformations are applied, and excludes any records filtered out by the transformations.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>source-record-write-total</td>
-<td>The number of records output written to Kafka for this task belonging to the named source connector in this worker, since the task was last restarted. This is after transformations are applied, and excludes any records filtered out by the transformations.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>transaction-size-avg</td>
-<td>The average number of records in the transactions the task has committed so far.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>transaction-size-max</td>
-<td>The number of records in the largest transaction the task has committed so far.</td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>transaction-size-min</td>
-<td>The number of records in the smallest transaction the task has committed so far. </td>
-<td>kafka.connect:type=source-task-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>deadletterqueue-produce-failures</td>
-<td>The number of failed writes to the dead letter queue.</td>
-<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>deadletterqueue-produce-requests</td>
-<td>The number of attempted writes to the dead letter queue.</td>
-<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>last-error-timestamp</td>
-<td>The epoch timestamp when this task last encountered an error.</td>
-<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>total-errors-logged</td>
-<td>The number of errors that were logged.</td>
-<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>total-record-errors</td>
-<td>The number of record processing errors in this task. </td>
-<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>total-record-failures</td>
-<td>The number of record processing failures in this task.</td>
-<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>total-records-skipped</td>
-<td>The number of records skipped due to errors.</td>
-<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-<tr>
-<td>total-retries</td>
-<td>The number of operations retried.</td>
-<td>kafka.connect:type=task-error-metrics,connector="{connector}",task="{task}"</td>
-</tr>
-</tbody></table>
diff --git a/content/en/43/generated/connect_predicates.html b/content/en/43/generated/connect_predicates.html
index 7a26dc6bb0..e69de29bb2 100644
--- a/content/en/43/generated/connect_predicates.html
+++ b/content/en/43/generated/connect_predicates.html
@@ -1,45 +0,0 @@
-<div id="org.apache.kafka.connect.transforms.predicates.HasHeaderKey">
-<h5><a href="#org.apache.kafka.connect.transforms.predicates.HasHeaderKey">org.apache.kafka.connect.transforms.predicates.HasHeaderKey</a></h5>
-A predicate which is true for records with at least one header with the configured name.
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="name"></a><a id="org.apache.kafka.connect.transforms.predicates.HasHeaderKey_name" href="#org.apache.kafka.connect.transforms.predicates.HasHeaderKey_name">name</a></h6>
-<p>The header name.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>non-empty string</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.predicates.RecordIsTombstone">
-<h5><a href="#org.apache.kafka.connect.transforms.predicates.RecordIsTombstone">org.apache.kafka.connect.transforms.predicates.RecordIsTombstone</a></h5>
-A predicate which is true for records which are tombstones (i.e. have null value).
-<p/>
-<ul class="config-list">
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.predicates.TopicNameMatches">
-<h5><a href="#org.apache.kafka.connect.transforms.predicates.TopicNameMatches">org.apache.kafka.connect.transforms.predicates.TopicNameMatches</a></h5>
-A predicate which is true for records with a topic name that matches the configured regular expression.
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="pattern"></a><a id="org.apache.kafka.connect.transforms.predicates.TopicNameMatches_pattern" href="#org.apache.kafka.connect.transforms.predicates.TopicNameMatches_pattern">pattern</a></h6>
-<p>A Java regular expression for matching against the name of a record's topic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>non-empty string, valid regex</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-
diff --git a/content/en/43/generated/connect_rest.yaml b/content/en/43/generated/connect_rest.yaml
index 3dbf5772a2..7a976861ab 100644
--- a/content/en/43/generated/connect_rest.yaml
+++ b/content/en/43/generated/connect_rest.yaml
@@ -8,7 +8,7 @@ info:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
title: Kafka Connect REST API
- version: 4.3.0
+ version: 4.3.1
paths:
/:
get:
diff --git a/content/en/43/generated/connect_transforms.html b/content/en/43/generated/connect_transforms.html
index 0c8798a3e3..e69de29bb2 100644
--- a/content/en/43/generated/connect_transforms.html
+++ b/content/en/43/generated/connect_transforms.html
@@ -1,549 +0,0 @@
-<div id="org.apache.kafka.connect.transforms.Cast">
-<h5><a href="#org.apache.kafka.connect.transforms.Cast">org.apache.kafka.connect.transforms.Cast</a></h5>
-Cast fields or the entire key or value to a specific type, e.g. to force an integer field to a smaller width. Cast from integers, floats, boolean and string to any other type, and cast binary to string (base64 encoded).<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.Cast$Key</code>) or value (<code>org.apache.kafka.connect.transforms.Cast$Value</code>).
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="spec"></a><a id="org.apache.kafka.connect.transforms.Cast_spec" href="#org.apache.kafka.connect.transforms.Cast_spec">spec</a></h6>
-<p>List of fields and the type to cast them to of the form field1:type,field2:type to cast fields of Maps or Structs. A single type to cast the entire value. Valid types are int8, int16, int32, int64, float32, float64, boolean, and string. Note that binary fields can only be cast to string.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>list of colon-delimited pairs, e.g. <code>foo:bar,abc:xyz</code></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.Cast_replace.null.with.default" href="#org.apache.kafka.connect.transforms.Cast_replace.null.with.default">replace.null.with.default</a></h6>
-<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.DropHeaders">
-<h5><a href="#org.apache.kafka.connect.transforms.DropHeaders">org.apache.kafka.connect.transforms.DropHeaders</a></h5>
-Removes one or more headers from each record.
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="headers"></a><a id="org.apache.kafka.connect.transforms.DropHeaders_headers" href="#org.apache.kafka.connect.transforms.DropHeaders_headers">headers</a></h6>
-<p>The name of the headers to be removed.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.ExtractField">
-<h5><a href="#org.apache.kafka.connect.transforms.ExtractField">org.apache.kafka.connect.transforms.ExtractField</a></h5>
-Extract the specified field from a Struct when schema present, or a Map in the case of schemaless data. Any null values are passed through unmodified.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.ExtractField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.ExtractField$Value</code>).
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="field"></a><a id="org.apache.kafka.connect.transforms.ExtractField_field" href="#org.apache.kafka.connect.transforms.ExtractField_field">field</a></h6>
-<p>Field name to extract.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="field.syntax.version"></a><a id="org.apache.kafka.connect.transforms.ExtractField_field.syntax.version" href="#org.apache.kafka.connect.transforms.ExtractField_field.syntax.version">field.syntax.version</a></h6>
-<p>Defines the version of the syntax to access fields. If set to <code>V1</code>, then the field paths are limited to access the elements at the root level of the struct or map. If set to <code>V2</code>, the syntax will support accessing nested elements. To access nested elements, dotted notation is used. If dots are already included in the field name, then backtick pairs can be used to wrap field names containing dots. E.g. to access the subfield <code>baz</code> from a field named "fo [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>V1</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [V1, V2]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.ExtractField_replace.null.with.default" href="#org.apache.kafka.connect.transforms.ExtractField_replace.null.with.default">replace.null.with.default</a></h6>
-<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.Filter">
-<h5><a href="#org.apache.kafka.connect.transforms.Filter">org.apache.kafka.connect.transforms.Filter</a></h5>
-Drops all records, filtering them from subsequent transformations in the chain. This is intended to be used conditionally to filter out records matching (or not matching) a particular Predicate.
-<p/>
-<ul class="config-list">
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.Flatten">
-<h5><a href="#org.apache.kafka.connect.transforms.Flatten">org.apache.kafka.connect.transforms.Flatten</a></h5>
-Flatten a nested data structure, generating names for each field by concatenating the field names at each level with a configurable delimiter character. Applies to Struct when schema present, or a Map in the case of schemaless data. Array fields and their contents are not modified. The default delimiter is '.'.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.Flatten$Key</code>) or value (<code>org.apache.kafka.connect.transfo [...]
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="delimiter"></a><a id="org.apache.kafka.connect.transforms.Flatten_delimiter" href="#org.apache.kafka.connect.transforms.Flatten_delimiter">delimiter</a></h6>
-<p>Delimiter to insert between field names from the input record when generating field names for the output record</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>.</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.HeaderFrom">
-<h5><a href="#org.apache.kafka.connect.transforms.HeaderFrom">org.apache.kafka.connect.transforms.HeaderFrom</a></h5>
-Moves or copies fields in the key/value of a record into that record's headers. Corresponding elements of <code>fields</code> and <code>headers</code> together identify a field and the header it should be moved or copied to. Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.HeaderFrom$Key</code>) or value (<code>org.apache.kafka.connect.transforms.HeaderFrom$Value</code>).
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="fields"></a><a id="org.apache.kafka.connect.transforms.HeaderFrom_fields" href="#org.apache.kafka.connect.transforms.HeaderFrom_fields">fields</a></h6>
-<p>Field names in the record whose values are to be copied or moved to headers.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>non-empty list</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="headers"></a><a id="org.apache.kafka.connect.transforms.HeaderFrom_headers" href="#org.apache.kafka.connect.transforms.HeaderFrom_headers">headers</a></h6>
-<p>Header names, in the same order as the field names listed in the fields configuration property.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>non-empty list</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="operation"></a><a id="org.apache.kafka.connect.transforms.HeaderFrom_operation" href="#org.apache.kafka.connect.transforms.HeaderFrom_operation">operation</a></h6>
-<p>Either <code>move</code> if the fields are to be moved to the headers (removed from the key/value), or <code>copy</code> if the fields are to be copied to the headers (retained in the key/value).</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>[move, copy]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.HeaderFrom_replace.null.with.default" href="#org.apache.kafka.connect.transforms.HeaderFrom_replace.null.with.default">replace.null.with.default</a></h6>
-<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.HoistField">
-<h5><a href="#org.apache.kafka.connect.transforms.HoistField">org.apache.kafka.connect.transforms.HoistField</a></h5>
-Wrap data using the specified field name in a Struct when schema present, or a Map in the case of schemaless data.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.HoistField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.HoistField$Value</code>).
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="field"></a><a id="org.apache.kafka.connect.transforms.HoistField_field" href="#org.apache.kafka.connect.transforms.HoistField_field">field</a></h6>
-<p>Field name for the single field that will be created in the resulting Struct or Map.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.InsertField">
-<h5><a href="#org.apache.kafka.connect.transforms.InsertField">org.apache.kafka.connect.transforms.InsertField</a></h5>
-Insert field(s) using attributes from the record metadata or a configured static value.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.InsertField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.InsertField$Value</code>).
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="offset.field"></a><a id="org.apache.kafka.connect.transforms.InsertField_offset.field" href="#org.apache.kafka.connect.transforms.InsertField_offset.field">offset.field</a></h6>
-<p>Field name for Kafka offset - only applicable to sink connectors.<br/>Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="partition.field"></a><a id="org.apache.kafka.connect.transforms.InsertField_partition.field" href="#org.apache.kafka.connect.transforms.InsertField_partition.field">partition.field</a></h6>
-<p>Field name for Kafka partition. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.InsertField_replace.null.with.default" href="#org.apache.kafka.connect.transforms.InsertField_replace.null.with.default">replace.null.with.default</a></h6>
-<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="static.field"></a><a id="org.apache.kafka.connect.transforms.InsertField_static.field" href="#org.apache.kafka.connect.transforms.InsertField_static.field">static.field</a></h6>
-<p>Field name for static data field. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="static.value"></a><a id="org.apache.kafka.connect.transforms.InsertField_static.value" href="#org.apache.kafka.connect.transforms.InsertField_static.value">static.value</a></h6>
-<p>Static field value, if field name configured.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="timestamp.field"></a><a id="org.apache.kafka.connect.transforms.InsertField_timestamp.field" href="#org.apache.kafka.connect.transforms.InsertField_timestamp.field">timestamp.field</a></h6>
-<p>Field name for record timestamp. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="topic.field"></a><a id="org.apache.kafka.connect.transforms.InsertField_topic.field" href="#org.apache.kafka.connect.transforms.InsertField_topic.field">topic.field</a></h6>
-<p>Field name for Kafka topic. Suffix with <code>!</code> to make this a required field, or <code>?</code> to keep it optional (the default).</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.InsertHeader">
-<h5><a href="#org.apache.kafka.connect.transforms.InsertHeader">org.apache.kafka.connect.transforms.InsertHeader</a></h5>
-Add a header to each record.
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="header"></a><a id="org.apache.kafka.connect.transforms.InsertHeader_header" href="#org.apache.kafka.connect.transforms.InsertHeader_header">header</a></h6>
-<p>The name of the header.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>non-null string</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="value.literal"></a><a id="org.apache.kafka.connect.transforms.InsertHeader_value.literal" href="#org.apache.kafka.connect.transforms.InsertHeader_value.literal">value.literal</a></h6>
-<p>The literal value that is to be set as the header value on all records.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>non-null string</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.MaskField">
-<h5><a href="#org.apache.kafka.connect.transforms.MaskField">org.apache.kafka.connect.transforms.MaskField</a></h5>
-Mask specified fields with a valid null value for the field type (i.e. 0, false, empty string, and so on).<p/>For numeric and string fields, an optional replacement value can be specified that is converted to the correct type.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.MaskField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.MaskField$Value</code>).
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="fields"></a><a id="org.apache.kafka.connect.transforms.MaskField_fields" href="#org.apache.kafka.connect.transforms.MaskField_fields">fields</a></h6>
-<p>Names of fields to mask.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.MaskField_replace.null.with.default" href="#org.apache.kafka.connect.transforms.MaskField_replace.null.with.default">replace.null.with.default</a></h6>
-<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replacement"></a><a id="org.apache.kafka.connect.transforms.MaskField_replacement" href="#org.apache.kafka.connect.transforms.MaskField_replacement">replacement</a></h6>
-<p>Custom value replacement, that will be applied to all 'fields' values (numeric or non-empty string values only).</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>non-empty string</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.RegexRouter">
-<h5><a href="#org.apache.kafka.connect.transforms.RegexRouter">org.apache.kafka.connect.transforms.RegexRouter</a></h5>
-Update the record topic using the configured regular expression and replacement string.<p/>Under the hood, the regex is compiled to a <code>java.util.regex.Pattern</code>. If the pattern matches the input topic, <code>java.util.regex.Matcher#replaceFirst()</code> is used with the replacement string to obtain the new topic.
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="regex"></a><a id="org.apache.kafka.connect.transforms.RegexRouter_regex" href="#org.apache.kafka.connect.transforms.RegexRouter_regex">regex</a></h6>
-<p>Regular expression to use for matching.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>valid regex</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replacement"></a><a id="org.apache.kafka.connect.transforms.RegexRouter_replacement" href="#org.apache.kafka.connect.transforms.RegexRouter_replacement">replacement</a></h6>
-<p>Replacement string.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.ReplaceField">
-<h5><a href="#org.apache.kafka.connect.transforms.ReplaceField">org.apache.kafka.connect.transforms.ReplaceField</a></h5>
-Filter or rename fields.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.ReplaceField$Key</code>) or value (<code>org.apache.kafka.connect.transforms.ReplaceField$Value</code>).
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="exclude"></a><a id="org.apache.kafka.connect.transforms.ReplaceField_exclude" href="#org.apache.kafka.connect.transforms.ReplaceField_exclude">exclude</a></h6>
-<p>Fields to exclude. This takes precedence over the fields to include.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="include"></a><a id="org.apache.kafka.connect.transforms.ReplaceField_include" href="#org.apache.kafka.connect.transforms.ReplaceField_include">include</a></h6>
-<p>Fields to include. If specified, only these fields will be used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="renames"></a><a id="org.apache.kafka.connect.transforms.ReplaceField_renames" href="#org.apache.kafka.connect.transforms.ReplaceField_renames">renames</a></h6>
-<p>Field rename mappings.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td>list of colon-delimited pairs, e.g. <code>foo:bar,abc:xyz</code></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.ReplaceField_replace.null.with.default" href="#org.apache.kafka.connect.transforms.ReplaceField_replace.null.with.default">replace.null.with.default</a></h6>
-<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.SetSchemaMetadata">
-<h5><a href="#org.apache.kafka.connect.transforms.SetSchemaMetadata">org.apache.kafka.connect.transforms.SetSchemaMetadata</a></h5>
-Set the schema name, version or both on the record's key (<code>org.apache.kafka.connect.transforms.SetSchemaMetadata$Key</code>) or value (<code>org.apache.kafka.connect.transforms.SetSchemaMetadata$Value</code>) schema.
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="schema.name"></a><a id="org.apache.kafka.connect.transforms.SetSchemaMetadata_schema.name" href="#org.apache.kafka.connect.transforms.SetSchemaMetadata_schema.name">schema.name</a></h6>
-<p>Schema name to set.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="schema.version"></a><a id="org.apache.kafka.connect.transforms.SetSchemaMetadata_schema.version" href="#org.apache.kafka.connect.transforms.SetSchemaMetadata_schema.version">schema.version</a></h6>
-<p>Schema version to set.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.SetSchemaMetadata_replace.null.with.default" href="#org.apache.kafka.connect.transforms.SetSchemaMetadata_replace.null.with.default">replace.null.with.default</a></h6>
-<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.TimestampConverter">
-<h5><a href="#org.apache.kafka.connect.transforms.TimestampConverter">org.apache.kafka.connect.transforms.TimestampConverter</a></h5>
-Convert timestamps between different formats such as Unix epoch, strings, and Connect Date/Timestamp types.Applies to individual fields or to the entire value.<p/>Use the concrete transformation type designed for the record key (<code>org.apache.kafka.connect.transforms.TimestampConverter$Key</code>) or value (<code>org.apache.kafka.connect.transforms.TimestampConverter$Value</code>).
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="target.type"></a><a id="org.apache.kafka.connect.transforms.TimestampConverter_target.type" href="#org.apache.kafka.connect.transforms.TimestampConverter_target.type">target.type</a></h6>
-<p>The desired timestamp representation: string, unix, Date, Time, or Timestamp</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>[string, unix, Date, Time, Timestamp]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="field"></a><a id="org.apache.kafka.connect.transforms.TimestampConverter_field" href="#org.apache.kafka.connect.transforms.TimestampConverter_field">field</a></h6>
-<p>The field containing the timestamp, or empty if the entire value is a timestamp</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="format"></a><a id="org.apache.kafka.connect.transforms.TimestampConverter_format" href="#org.apache.kafka.connect.transforms.TimestampConverter_format">format</a></h6>
-<p>A SimpleDateFormat-compatible format for the timestamp. Used to generate the output when type=string or used to parse the input if the input is a string.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.TimestampConverter_replace.null.with.default" href="#org.apache.kafka.connect.transforms.TimestampConverter_replace.null.with.default">replace.null.with.default</a></h6>
-<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="unix.precision"></a><a id="org.apache.kafka.connect.transforms.TimestampConverter_unix.precision" href="#org.apache.kafka.connect.transforms.TimestampConverter_unix.precision">unix.precision</a></h6>
-<p>The desired Unix precision for the timestamp: seconds, milliseconds, microseconds, or nanoseconds. Used to generate the output when type=unix or used to parse the input if the input is a Long.Note: This SMT will cause precision loss during conversions from, and to, values with sub-millisecond components.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>milliseconds</td></tr>
-<tr><th>Valid Values:</th><td>[nanoseconds, microseconds, milliseconds, seconds]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.TimestampRouter">
-<h5><a href="#org.apache.kafka.connect.transforms.TimestampRouter">org.apache.kafka.connect.transforms.TimestampRouter</a></h5>
-Update the record's topic field as a function of the original topic value and the record timestamp.<p/>This is mainly useful for sink connectors, since the topic field is often used to determine the equivalent entity name in the destination system(e.g. database table or search index name).
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="timestamp.format"></a><a id="org.apache.kafka.connect.transforms.TimestampRouter_timestamp.format" href="#org.apache.kafka.connect.transforms.TimestampRouter_timestamp.format">timestamp.format</a></h6>
-<p>Format string for the timestamp that is compatible with <code>java.text.SimpleDateFormat</code>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>yyyyMMdd</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="topic.format"></a><a id="org.apache.kafka.connect.transforms.TimestampRouter_topic.format" href="#org.apache.kafka.connect.transforms.TimestampRouter_topic.format">topic.format</a></h6>
-<p>Format string which can contain <code>${topic}</code> and <code>${timestamp}</code> as placeholders for the topic and timestamp, respectively.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>${topic}-${timestamp}</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-<div id="org.apache.kafka.connect.transforms.ValueToKey">
-<h5><a href="#org.apache.kafka.connect.transforms.ValueToKey">org.apache.kafka.connect.transforms.ValueToKey</a></h5>
-Replace the record key with a new key formed from a subset of fields in the record value.
-<p/>
-<ul class="config-list">
-<li>
-<h6><a id="fields"></a><a id="org.apache.kafka.connect.transforms.ValueToKey_fields" href="#org.apache.kafka.connect.transforms.ValueToKey_fields">fields</a></h6>
-<p>Field names on the record value to extract as the record key.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h6><a id="replace.null.with.default"></a><a id="org.apache.kafka.connect.transforms.ValueToKey_replace.null.with.default" href="#org.apache.kafka.connect.transforms.ValueToKey_replace.null.with.default">replace.null.with.default</a></h6>
-<p>Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
-</div>
-
diff --git a/content/en/43/generated/consumer_config.html b/content/en/43/generated/consumer_config.html
index c3a539468e..e69de29bb2 100644
--- a/content/en/43/generated/consumer_config.html
+++ b/content/en/43/generated/consumer_config.html
@@ -1,1153 +0,0 @@
-<ul class="config-list">
-<li>
-<h4><a id="bootstrap.servers"></a><a id="consumerconfigs_bootstrap.servers" href="#consumerconfigs_bootstrap.servers">bootstrap.servers</a></h4>
-<p>A list of host/port pairs used to establish the initial connection to the Kafka cluster. Clients use this list to bootstrap and discover the full set of Kafka brokers. While the order of servers in the list does not matter, we recommend including more than one server to ensure resilience if any servers are down. This list does not need to contain the entire set of brokers, as Kafka clients automatically manage and update connections to the cluster efficiently. This list must be in the [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="key.deserializer"></a><a id="consumerconfigs_key.deserializer" href="#consumerconfigs_key.deserializer">key.deserializer</a></h4>
-<p>Deserializer class for key that implements the <code>org.apache.kafka.common.serialization.Deserializer</code> interface.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="value.deserializer"></a><a id="consumerconfigs_value.deserializer" href="#consumerconfigs_value.deserializer">value.deserializer</a></h4>
-<p>Deserializer class for value that implements the <code>org.apache.kafka.common.serialization.Deserializer</code> interface.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="fetch.min.bytes"></a><a id="consumerconfigs_fetch.min.bytes" href="#consumerconfigs_fetch.min.bytes">fetch.min.bytes</a></h4>
-<p>The minimum amount of data the server should return for a fetch request. If insufficient data is available the request will wait for that much data to accumulate before answering the request. The default setting of 1 byte means that fetch requests are answered as soon as that many byte(s) of data is available or the fetch request times out waiting for data to arrive. Setting this to a larger value will cause the server to wait for larger amounts of data to accumulate which can improve [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.id"></a><a id="consumerconfigs_group.id" href="#consumerconfigs_group.id">group.id</a></h4>
-<p>A unique string that identifies the consumer group this consumer belongs to. This property is required if the consumer uses either the group management functionality by using <code>subscribe(topic)</code> or the Kafka-based offset management strategy.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.protocol"></a><a id="consumerconfigs_group.protocol" href="#consumerconfigs_group.protocol">group.protocol</a></h4>
-<p>The group protocol that the consumer uses. The supported values are <code>classic</code> or <code>consumer</code>. The default value is <code>classic</code>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>classic</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [CONSUMER, CLASSIC]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="heartbeat.interval.ms"></a><a id="consumerconfigs_heartbeat.interval.ms" href="#consumerconfigs_heartbeat.interval.ms">heartbeat.interval.ms</a></h4>
-<p>The expected time between heartbeats to the consumer coordinator when using Kafka's group management facilities. Heartbeats are used to ensure that the consumer's session stays active and to facilitate rebalancing when new consumers join or leave the group. This config is only supported if <code>group.protocol</code> is set to "classic". In that case, the value must be set lower than <code>session.timeout.ms</code>, but typically should be set no higher than 1/3 of that value. It can [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>3000 (3 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="max.partition.fetch.bytes"></a><a id="consumerconfigs_max.partition.fetch.bytes" href="#consumerconfigs_max.partition.fetch.bytes">max.partition.fetch.bytes</a></h4>
-<p>The maximum amount of data per-partition the server will return. Records are fetched in batches by the consumer. If the first record batch in the first non-empty partition of the fetch is larger than this limit, the batch will still be returned to ensure that the consumer can make progress. The maximum record batch size accepted by the broker is defined via <code>message.max.bytes</code> (broker config) or <code>max.message.bytes</code> (topic config). See fetch.max.bytes for limiting [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1048576 (1 mebibyte)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="session.timeout.ms"></a><a id="consumerconfigs_session.timeout.ms" href="#consumerconfigs_session.timeout.ms">session.timeout.ms</a></h4>
-<p>The timeout used to detect client failures when using Kafka's group management facility. The client sends periodic heartbeats to indicate its liveness to the broker. If no heartbeats are received by the broker before the expiration of this session timeout, then the broker will remove this client from the group and initiate a rebalance. Note that the value must be in the allowable range as configured in the broker configuration by <code>group.min.session.timeout.ms</code> and <code>gro [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.key.password"></a><a id="consumerconfigs_ssl.key.password" href="#consumerconfigs_ssl.key.password">ssl.key.password</a></h4>
-<p>The password of the private key in the key store file or the PEM key specified in 'ssl.keystore.key'.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.certificate.chain"></a><a id="consumerconfigs_ssl.keystore.certificate.chain" href="#consumerconfigs_ssl.keystore.certificate.chain">ssl.keystore.certificate.chain</a></h4>
-<p>Certificate chain in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with a list of X.509 certificates</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.key"></a><a id="consumerconfigs_ssl.keystore.key" href="#consumerconfigs_ssl.keystore.key">ssl.keystore.key</a></h4>
-<p>Private key in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with PKCS#8 keys. If the key is encrypted, key password must be specified using 'ssl.key.password'</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.location"></a><a id="consumerconfigs_ssl.keystore.location" href="#consumerconfigs_ssl.keystore.location">ssl.keystore.location</a></h4>
-<p>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.password"></a><a id="consumerconfigs_ssl.keystore.password" href="#consumerconfigs_ssl.keystore.password">ssl.keystore.password</a></h4>
-<p>The store password for the key store file. This is optional for client and only needed if 'ssl.keystore.location' is configured. Key store password is not supported for PEM format.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.certificates"></a><a id="consumerconfigs_ssl.truststore.certificates" href="#consumerconfigs_ssl.truststore.certificates">ssl.truststore.certificates</a></h4>
-<p>Trusted certificates in the format specified by 'ssl.truststore.type'. Default SSL engine factory supports only PEM format with X.509 certificates.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.location"></a><a id="consumerconfigs_ssl.truststore.location" href="#consumerconfigs_ssl.truststore.location">ssl.truststore.location</a></h4>
-<p>The location of the trust store file.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.password"></a><a id="consumerconfigs_ssl.truststore.password" href="#consumerconfigs_ssl.truststore.password">ssl.truststore.password</a></h4>
-<p>The password for the trust store file. If a password is not set, trust store file configured will still be used, but integrity checking is disabled. Trust store password is not supported for PEM format.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="allow.auto.create.topics"></a><a id="consumerconfigs_allow.auto.create.topics" href="#consumerconfigs_allow.auto.create.topics">allow.auto.create.topics</a></h4>
-<p>Allow automatic topic creation on the broker when subscribing to or assigning a topic. A topic being subscribed to will be automatically created only if the broker allows for it using <code>auto.create.topics.enable</code> broker configuration.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="auto.offset.reset"></a><a id="consumerconfigs_auto.offset.reset" href="#consumerconfigs_auto.offset.reset">auto.offset.reset</a></h4>
-<p>What to do when there is no initial offset in Kafka or if the current offset does not exist any more on the server (e.g. because that data has been deleted): <ul><li>earliest: automatically reset the offset to the earliest offset</li><li>latest: automatically reset the offset to the latest offset</li><li>by_duration:<duration>: automatically reset the offset to a configured <duration> from the current timestamp. <duration> must be specified in ISO8601 format (PnDTnHn [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>latest</td></tr>
-<tr><th>Valid Values:</th><td>[latest, earliest, none, by_duration:PnDTnHnMn.nS]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="client.dns.lookup"></a><a id="consumerconfigs_client.dns.lookup" href="#consumerconfigs_client.dns.lookup">client.dns.lookup</a></h4>
-<p>Controls how the client uses DNS lookups. If set to <code>use_all_dns_ips</code>, connect to each returned IP address in sequence until a successful connection is established. After a disconnection, the next IP is used. Once all IPs have been used once, the client resolves the IP(s) from the hostname again (both the JVM and the OS cache DNS name lookups, however). If set to <code>resolve_canonical_bootstrap_servers_only</code>, resolve each bootstrap address into a list of canonical n [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>use_all_dns_ips</td></tr>
-<tr><th>Valid Values:</th><td>[use_all_dns_ips, resolve_canonical_bootstrap_servers_only]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="connections.max.idle.ms"></a><a id="consumerconfigs_connections.max.idle.ms" href="#consumerconfigs_connections.max.idle.ms">connections.max.idle.ms</a></h4>
-<p>Close idle connections after the number of milliseconds specified by this config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>540000 (9 minutes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="default.api.timeout.ms"></a><a id="consumerconfigs_default.api.timeout.ms" href="#consumerconfigs_default.api.timeout.ms">default.api.timeout.ms</a></h4>
-<p>Specifies the timeout (in milliseconds) for client APIs. This configuration is used as the default timeout for all client operations that do not specify a <code>timeout</code> parameter.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="enable.auto.commit"></a><a id="consumerconfigs_enable.auto.commit" href="#consumerconfigs_enable.auto.commit">enable.auto.commit</a></h4>
-<p>If true the consumer's offset will be periodically committed in the background.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="exclude.internal.topics"></a><a id="consumerconfigs_exclude.internal.topics" href="#consumerconfigs_exclude.internal.topics">exclude.internal.topics</a></h4>
-<p>Whether internal topics matching a subscribed pattern should be excluded from the subscription. It is always possible to explicitly subscribe to an internal topic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="fetch.max.bytes"></a><a id="consumerconfigs_fetch.max.bytes" href="#consumerconfigs_fetch.max.bytes">fetch.max.bytes</a></h4>
-<p>The maximum amount of data the server should return for a fetch request. Records are fetched in batches by the consumer, and if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that the consumer can make progress. As such, this is not a absolute maximum. The maximum record batch size accepted by the broker is defined via <code>message.max.bytes</code> (broker config) or <code>max.message.b [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>52428800 (50 mebibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.instance.id"></a><a id="consumerconfigs_group.instance.id" href="#consumerconfigs_group.instance.id">group.instance.id</a></h4>
-<p>A unique identifier of the consumer instance provided by the end user. Only non-empty strings are permitted. If set, the consumer is treated as a static member, which means that only one instance with this ID is allowed in the consumer group at any time. This can be used in combination with a larger session timeout to avoid group rebalances caused by transient unavailability (e.g. process restarts). If not set, the consumer will join the group as a dynamic member, which is the traditi [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>non-empty string</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.remote.assignor"></a><a id="consumerconfigs_group.remote.assignor" href="#consumerconfigs_group.remote.assignor">group.remote.assignor</a></h4>
-<p>The name of the server-side assignor to use. If not specified, the group coordinator will pick the first assignor defined in the broker config group.consumer.assignors.This configuration is applied only if <code>group.protocol</code> is set to "consumer".</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="isolation.level"></a><a id="consumerconfigs_isolation.level" href="#consumerconfigs_isolation.level">isolation.level</a></h4>
-<p>Controls how to read messages written transactionally. If set to <code>read_committed</code>, consumer.poll() will only return transactional messages which have been committed. If set to <code>read_uncommitted</code> (the default), consumer.poll() will return all messages, even transactional messages which have been aborted. Non-transactional messages will be returned unconditionally in either mode. <p>Messages will always be returned in offset order. Hence, in <code>read_committed</ [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>read_uncommitted</td></tr>
-<tr><th>Valid Values:</th><td>[read_committed, read_uncommitted]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="max.poll.interval.ms"></a><a id="consumerconfigs_max.poll.interval.ms" href="#consumerconfigs_max.poll.interval.ms">max.poll.interval.ms</a></h4>
-<p>The maximum delay between invocations of poll() when using consumer group management. This places an upper bound on the amount of time that the consumer can be idle before fetching more records. If poll() is not called before expiration of this timeout, then the consumer is considered failed and the group will rebalance in order to reassign the partitions to another member. For consumers using a non-null <code>group.instance.id</code> which reach this timeout, partitions will not be i [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="max.poll.records"></a><a id="consumerconfigs_max.poll.records" href="#consumerconfigs_max.poll.records">max.poll.records</a></h4>
-<p>The maximum number of records returned in a single call to poll(). Note, that <code>max.poll.records</code> does not impact the underlying fetching behavior. The consumer will cache the records from each fetch request and returns them incrementally from each poll.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>500</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="partition.assignment.strategy"></a><a id="consumerconfigs_partition.assignment.strategy" href="#consumerconfigs_partition.assignment.strategy">partition.assignment.strategy</a></h4>
-<p>A list of class names or class types, ordered by preference, of supported partition assignment strategies that the client will use to distribute partition ownership amongst consumer instances when group management is used. Available options are:<ul><li><code>org.apache.kafka.clients.consumer.RangeAssignor</code>: Assigns partitions on a per-topic basis.</li><li><code>org.apache.kafka.clients.consumer.RoundRobinAssignor</code>: Assigns partitions to consumers in a round-robin fashion.< [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>class org.apache.kafka.clients.consumer.RangeAssignor,class org.apache.kafka.clients.consumer.CooperativeStickyAssignor</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="receive.buffer.bytes"></a><a id="consumerconfigs_receive.buffer.bytes" href="#consumerconfigs_receive.buffer.bytes">receive.buffer.bytes</a></h4>
-<p>The size of the TCP receive buffer (SO_RCVBUF) to use when reading data. If the value is -1, the OS default will be used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>65536 (64 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="request.timeout.ms"></a><a id="consumerconfigs_request.timeout.ms" href="#consumerconfigs_request.timeout.ms">request.timeout.ms</a></h4>
-<p>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.client.callback.handler.class"></a><a id="consumerconfigs_sasl.client.callback.handler.class" href="#consumerconfigs_sasl.client.callback.handler.class">sasl.client.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.jaas.config"></a><a id="consumerconfigs_sasl.jaas.config" href="#consumerconfigs_sasl.jaas.config">sasl.jaas.config</a></h4>
-<p>JAAS login context parameters for SASL connections in the format used by JAAS configuration files. JAAS configuration file format is described <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html">here</a>. The format for the value is: <code>loginModuleClass controlFlag (optionName=optionValue)*;</code>. For brokers, the config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.service.name"></a><a id="consumerconfigs_sasl.kerberos.service.name" href="#consumerconfigs_sasl.kerberos.service.name">sasl.kerberos.service.name</a></h4>
-<p>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.callback.handler.class"></a><a id="consumerconfigs_sasl.login.callback.handler.class" href="#consumerconfigs_sasl.login.callback.handler.class">sasl.login.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL login callback handler class that implements the AuthenticateCallbackHandler interface. For brokers, login callback handler config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.callback.handler.class=com.example.CustomScramLoginCallbackHandler</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.class"></a><a id="consumerconfigs_sasl.login.class" href="#consumerconfigs_sasl.login.class">sasl.login.class</a></h4>
-<p>The fully qualified name of a class that implements the Login interface. For brokers, login config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.class=com.example.CustomScramLogin</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.mechanism"></a><a id="consumerconfigs_sasl.mechanism" href="#consumerconfigs_sasl.mechanism">sasl.mechanism</a></h4>
-<p>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>GSSAPI</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.algorithm"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.algorithm" href="#consumerconfigs_sasl.oauthbearer.assertion.algorithm">sasl.oauthbearer.assertion.algorithm</a></h4>
-<p><p>The algorithm the Apache Kafka client should use to sign the assertion sent to the identity provider. It is also used as the value of the OAuth <code>alg</code> (Algorithm) header in the JWT assertion.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>RS256</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [ES256, RS256]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.aud"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.claim.aud" href="#consumerconfigs_sasl.oauthbearer.assertion.claim.aud">sasl.oauthbearer.assertion.claim.aud</a></h4>
-<p><p>The JWT <code>aud</code> (Audience) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.iss"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.claim.iss" href="#consumerconfigs_sasl.oauthbearer.assertion.claim.iss">sasl.oauthbearer.assertion.claim.iss</a></h4>
-<p><p>The value to be used as the <code>iss</code> (Issuer) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.jti.include"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.claim.jti.include" href="#consumerconfigs_sasl.oauthbearer.assertion.claim.jti.include">sasl.oauthbearer.assertion.claim.jti.include</a></h4>
-<p><p>Flag that determines if the JWT assertion should generate a unique ID for the JWT and include it in the <code>jti</code> (JWT ID) claim.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.sub"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.claim.sub" href="#consumerconfigs_sasl.oauthbearer.assertion.claim.sub">sasl.oauthbearer.assertion.claim.sub</a></h4>
-<p><p>The value to be used as the <code>sub</code> (Subject) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.file"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.file" href="#consumerconfigs_sasl.oauthbearer.assertion.file">sasl.oauthbearer.assertion.file</a></h4>
-<p><p>File that contains a <em>pre-generated</em> JWT assertion.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect whenthe file changes to allow for the file to be reloaded on modifications. This allows for "live" assertion rotation without restarting the Kafka client.</p><p>The file contains the assertion in the serialized, three part JWT format:</p><ol><li>The <em>hea [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.private.key.file"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.private.key.file" href="#consumerconfigs_sasl.oauthbearer.assertion.private.key.file">sasl.oauthbearer.assertion.private.key.file</a></h4>
-<p><p>File that contains a private key in the standard PEM format which is used to sign the JWT assertion sent to the identity provider.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect when the file changes to allow for the file to be reloaded on modifications. This allows for "live" private key rotation without restarting the Kafka client.</p><p><em>Note</em>: If a v [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.private.key.passphrase"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.private.key.passphrase" href="#consumerconfigs_sasl.oauthbearer.assertion.private.key.passphrase">sasl.oauthbearer.assertion.private.key.passphrase</a></h4>
-<p><p>The optional passphrase to decrypt the private key file specified by <code>sasl.oauthbearer.assertion.private.key.file</code>.</p><p><em>Note</em>: If the file referred to by <code>sasl.oauthbearer.assertion.private.key.file</code> is modified on the file system at runtime and it was created with a <em>different</em> passphrase than it was previously, the client will not be able to access the private key file because the passphrase is now out of date. For that reason, when using pr [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.template.file"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.template.file" href="#consumerconfigs_sasl.oauthbearer.assertion.template.file">sasl.oauthbearer.assertion.template.file</a></h4>
-<p><p>This optional configuration specifies the file containing the JWT headers and/or payload claims to be used when creating the JWT assertion.</p><p>Not all identity providers require the same set of claims; some may require a given claim while others may prohibit it. In order to provide the most flexibility, this configuration allows the user to provide the static header values and claims that are to be included in the JWT.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.a [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.client.credentials.client.id"></a><a id="consumerconfigs_sasl.oauthbearer.client.credentials.client.id" href="#consumerconfigs_sasl.oauthbearer.client.credentials.client.id">sasl.oauthbearer.client.credentials.client.id</a></h4>
-<p><p>The ID (defined in/by the OAuth identity provider) to identify the client requesting the token.</p><p>The client ID was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientId</code>. For backward compatibility, the <code>clientId</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.client.credentials.client.id</code> from conf [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.client.credentials.client.secret"></a><a id="consumerconfigs_sasl.oauthbearer.client.credentials.client.secret" href="#consumerconfigs_sasl.oauthbearer.client.credentials.client.secret">sasl.oauthbearer.client.credentials.client.secret</a></h4>
-<p><p>The secret (defined by either the user or preassigned, depending on the identity provider) of the client requesting the token.</p><p>The client secret was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientSecret</code>. For backward compatibility, the <code>clientSecret</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.cl [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.url"></a><a id="consumerconfigs_sasl.oauthbearer.jwks.endpoint.url" href="#consumerconfigs_sasl.oauthbearer.jwks.endpoint.url">sasl.oauthbearer.jwks.endpoint.url</a></h4>
-<p>The OAuth/OIDC provider URL from which the provider's <a href="https://datatracker.ietf.org/doc/html/rfc7517#section-5">JWKS (JSON Web Key Set)</a> can be retrieved. The URL can be HTTP(S)-based or file-based. If the URL is HTTP(S)-based, the JWKS data will be retrieved from the OAuth/OIDC provider via the configured URL on broker startup. All then-current keys will be cached on the broker for incoming requests. If an authentication request is received for a JWT that includes a "kid" [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwt.retriever.class"></a><a id="consumerconfigs_sasl.oauthbearer.jwt.retriever.class" href="#consumerconfigs_sasl.oauthbearer.jwt.retriever.class">sasl.oauthbearer.jwt.retriever.class</a></h4>
-<p><p>The fully-qualified class name of a <code>JwtRetriever</code> implementation used to request tokens from the identity provider.</p><p>The default configuration value represents a class that maintains backward compatibility with previous versions of Apache Kafka. The default implementation uses the configuration to determine which concrete implementation to create.<p>Other implementations that are provided include:</p><ul><li><code>org.apache.kafka.common.security.oauthbearer.Client [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtRetriever</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwt.validator.class"></a><a id="consumerconfigs_sasl.oauthbearer.jwt.validator.class" href="#consumerconfigs_sasl.oauthbearer.jwt.validator.class">sasl.oauthbearer.jwt.validator.class</a></h4>
-<p><p>The fully-qualified class name of a <code>JwtValidator</code> implementation used to validate the JWT from the identity provider.</p><p>The default validator (<code>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</code>) maintains backward compatibility with previous versions of Apache Kafka. The default validator uses configuration to determine which concrete implementation to create.<p>The built-in <code>JwtValidator</code> implementations are:</p><ul><li><code>o [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.scope"></a><a id="consumerconfigs_sasl.oauthbearer.scope" href="#consumerconfigs_sasl.oauthbearer.scope">sasl.oauthbearer.scope</a></h4>
-<p><p>This is the level of access a client application is granted to a resource or API which is included in the token request. If provided, it should match one or more scopes configured in the identity provider.</p><p>The scope was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>scope</code>. For backward compatibility, the <code>scope</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p> [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.token.endpoint.url"></a><a id="consumerconfigs_sasl.oauthbearer.token.endpoint.url" href="#consumerconfigs_sasl.oauthbearer.token.endpoint.url">sasl.oauthbearer.token.endpoint.url</a></h4>
-<p>The URL for the OAuth/OIDC identity provider. If the URL is HTTP(S)-based, it is the issuer's token endpoint URL to which requests will be made to login based on the configuration in <code>sasl.oauthbearer.jwt.retriever.class</code>. If the URL is file-based, it specifies a file containing an access token (in JWT serialized form) issued by the OAuth/OIDC identity provider to use for authorization.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="security.protocol"></a><a id="consumerconfigs_security.protocol" href="#consumerconfigs_security.protocol">security.protocol</a></h4>
-<p>Protocol used to communicate with brokers.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>PLAINTEXT</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [SASL_SSL, PLAINTEXT, SSL, SASL_PLAINTEXT]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="send.buffer.bytes"></a><a id="consumerconfigs_send.buffer.bytes" href="#consumerconfigs_send.buffer.bytes">send.buffer.bytes</a></h4>
-<p>The size of the TCP send buffer (SO_SNDBUF) to use when sending data. If the value is -1, the OS default will be used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>131072 (128 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.acknowledgement.mode"></a><a id="consumerconfigs_share.acknowledgement.mode" href="#consumerconfigs_share.acknowledgement.mode">share.acknowledgement.mode</a></h4>
-<p>Controls the acknowledgement mode for a share consumer. If set to <code>implicit</code>, the acknowledgement mode of the consumer is implicit and it must not use <code>org.apache.kafka.clients.consumer.ShareConsumer.acknowledge()</code> to acknowledge delivery of records. Instead, delivery is acknowledged implicitly on the next call to poll or commit. If set to <code>explicit</code>, the acknowledgement mode of the consumer is explicit and it must use <code>org.apache.kafka.clients.co [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>implicit</td></tr>
-<tr><th>Valid Values:</th><td>[implicit, explicit]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.acquire.mode"></a><a id="consumerconfigs_share.acquire.mode" href="#consumerconfigs_share.acquire.mode">share.acquire.mode</a></h4>
-<p>Controls the acquire mode for a share consumer. If set to <code>record_limit</code>, the number of records returned in each poll() will not exceed the value of <code>max.poll.records</code>. If set to <code>batch_optimized</code>, the number of records returned in each poll() call may exceed <code>max.poll.records</code> to align with batch boundaries for optimization.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>BATCH_OPTIMIZED</td></tr>
-<tr><th>Valid Values:</th><td>[batch_optimized, record_limit]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.connection.setup.timeout.max.ms"></a><a id="consumerconfigs_socket.connection.setup.timeout.max.ms" href="#consumerconfigs_socket.connection.setup.timeout.max.ms">socket.connection.setup.timeout.max.ms</a></h4>
-<p>The maximum amount of time the client will wait for the socket connection to be established. The connection setup timeout will increase exponentially for each consecutive connection failure up to this maximum. To avoid connection storms, a randomization factor of 0.2 will be applied to the timeout resulting in a random range between 20% below and 20% above the computed value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.connection.setup.timeout.ms"></a><a id="consumerconfigs_socket.connection.setup.timeout.ms" href="#consumerconfigs_socket.connection.setup.timeout.ms">socket.connection.setup.timeout.ms</a></h4>
-<p>The amount of time the client will wait for the socket connection to be established. If the connection is not built before the timeout elapses, clients will close the socket channel. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>socket.connection.setup.timeout.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.enabled.protocols"></a><a id="consumerconfigs_ssl.enabled.protocols" href="#consumerconfigs_ssl.enabled.protocols">ssl.enabled.protocols</a></h4>
-<p>The list of protocols enabled for SSL connections. The default is 'TLSv1.2,TLSv1.3'. This means that clients and servers will prefer TLSv1.3 if both support it and fallback to TLSv1.2 otherwise (assuming both support at least TLSv1.2). This default should be fine for most use cases. If this configuration is set to an empty list, Kafka will use the protocols enabled by default in the underlying SSLEngine, which may include additional protocols depending on the JVM version. Also see the [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>TLSv1.2,TLSv1.3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.type"></a><a id="consumerconfigs_ssl.keystore.type" href="#consumerconfigs_ssl.keystore.type">ssl.keystore.type</a></h4>
-<p>The file format of the key store file. This is optional for client. The values currently supported by the default <code>ssl.engine.factory.class</code> are [JKS, PKCS12, PEM].</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>JKS</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.protocol"></a><a id="consumerconfigs_ssl.protocol" href="#consumerconfigs_ssl.protocol">ssl.protocol</a></h4>
-<p>The SSL protocol used to generate the SSLContext. The default is 'TLSv1.3', which should be fine for most use cases. A typical alternative to the default is 'TLSv1.2'. Allowed values for this config are dependent on the JVM. Clients using the defaults for this config and 'ssl.enabled.protocols' will downgrade to 'TLSv1.2' if the server does not support 'TLSv1.3'. If this config is set to 'TLSv1.2', however, clients will not use 'TLSv1.3' even if it is one of the values in <code>ssl.en [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>TLSv1.3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.provider"></a><a id="consumerconfigs_ssl.provider" href="#consumerconfigs_ssl.provider">ssl.provider</a></h4>
-<p>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.type"></a><a id="consumerconfigs_ssl.truststore.type" href="#consumerconfigs_ssl.truststore.type">ssl.truststore.type</a></h4>
-<p>The file format of the trust store file. The values currently supported by the default <code>ssl.engine.factory.class</code> are [JKS, PKCS12, PEM].</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>JKS</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="auto.commit.interval.ms"></a><a id="consumerconfigs_auto.commit.interval.ms" href="#consumerconfigs_auto.commit.interval.ms">auto.commit.interval.ms</a></h4>
-<p>The frequency in milliseconds that the consumer offsets are auto-committed to Kafka if <code>enable.auto.commit</code> is set to <code>true</code>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="check.crcs"></a><a id="consumerconfigs_check.crcs" href="#consumerconfigs_check.crcs">check.crcs</a></h4>
-<p>Automatically check the CRC32 of the records consumed. This ensures no on-the-wire or on-disk corruption to the messages occurred. This check adds some overhead, so it may be disabled in cases seeking extreme performance.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="client.id"></a><a id="consumerconfigs_client.id" href="#consumerconfigs_client.id">client.id</a></h4>
-<p>An id string to pass to the server when making requests. The purpose of this is to be able to track the source of requests beyond just ip/port by allowing a logical application name to be included in server-side request logging.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="client.rack"></a><a id="consumerconfigs_client.rack" href="#consumerconfigs_client.rack">client.rack</a></h4>
-<p>A rack identifier for this client. This can be any string value which indicates where this client is physically located. It corresponds with the broker config 'broker.rack'</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="config.providers"></a><a id="consumerconfigs_config.providers" href="#consumerconfigs_config.providers">config.providers</a></h4>
-<p>Comma-separated alias names for classes implementing the <code>ConfigProvider</code> interface. This enables loading configuration data (such as passwords, API keys, and other credentials) from external sources. For example, see <a href="https://kafka.apache.org/documentation/#config_providers">Configuration Providers</a>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="enable.metrics.push"></a><a id="consumerconfigs_enable.metrics.push" href="#consumerconfigs_enable.metrics.push">enable.metrics.push</a></h4>
-<p>Whether to enable pushing of client metrics to the cluster, if the cluster has a client metrics subscription which matches this client.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="fetch.max.wait.ms"></a><a id="consumerconfigs_fetch.max.wait.ms" href="#consumerconfigs_fetch.max.wait.ms">fetch.max.wait.ms</a></h4>
-<p>The maximum amount of time the server will block before answering the fetch request there isn't sufficient data to immediately satisfy the requirement given by fetch.min.bytes. This config is used only for local log fetch. To tune the remote fetch maximum wait time, please refer to 'remote.fetch.max.wait.ms' broker config</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>500</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="interceptor.classes"></a><a id="consumerconfigs_interceptor.classes" href="#consumerconfigs_interceptor.classes">interceptor.classes</a></h4>
-<p>A list of classes to use as interceptors. Implementing the <code>org.apache.kafka.clients.consumer.ConsumerInterceptor</code> interface allows you to intercept (and possibly mutate) records received by the consumer. By default, there are no interceptors.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.max.age.ms"></a><a id="consumerconfigs_metadata.max.age.ms" href="#consumerconfigs_metadata.max.age.ms">metadata.max.age.ms</a></h4>
-<p>The period of time in milliseconds after which we force a refresh of metadata even if we haven't seen any partition leadership changes to proactively discover any new brokers or partitions.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.recovery.rebootstrap.trigger.ms"></a><a id="consumerconfigs_metadata.recovery.rebootstrap.trigger.ms" href="#consumerconfigs_metadata.recovery.rebootstrap.trigger.ms">metadata.recovery.rebootstrap.trigger.ms</a></h4>
-<p>If a client configured to rebootstrap using <code>metadata.recovery.strategy=rebootstrap</code> is unable to obtain metadata from any of the brokers in the last known metadata for this interval, client repeats the bootstrap process using <code>bootstrap.servers</code> configuration.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.recovery.strategy"></a><a id="consumerconfigs_metadata.recovery.strategy" href="#consumerconfigs_metadata.recovery.strategy">metadata.recovery.strategy</a></h4>
-<p>Controls how the client recovers when none of the brokers known to it is available. If set to <code>none</code>, the client fails. If set to <code>rebootstrap</code>, the client repeats the bootstrap process using <code>bootstrap.servers</code>. Rebootstrapping is useful when a client communicates with brokers so infrequently that the set of brokers may change entirely before the client refreshes metadata. Metadata recovery is triggered when all last-known brokers appear unavailable s [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>rebootstrap</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [REBOOTSTRAP, NONE]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metric.reporters"></a><a id="consumerconfigs_metric.reporters" href="#consumerconfigs_metric.reporters">metric.reporters</a></h4>
-<p>A list of classes to use as metrics reporters. Implementing the <code>org.apache.kafka.common.metrics.MetricsReporter</code> interface allows plugging in classes that will be notified of new metric creation. When custom reporters are set and <code>org.apache.kafka.common.metrics.JmxReporter</code> is needed, it has to be explicitly added to the list.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.metrics.JmxReporter</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.num.samples"></a><a id="consumerconfigs_metrics.num.samples" href="#consumerconfigs_metrics.num.samples">metrics.num.samples</a></h4>
-<p>The number of samples maintained to compute metrics.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.recording.level"></a><a id="consumerconfigs_metrics.recording.level" href="#consumerconfigs_metrics.recording.level">metrics.recording.level</a></h4>
-<p>The highest recording level for metrics. It has three levels for recording metrics - info, debug, and trace.<br> <br>INFO level records only essential metrics necessary for monitoring system performance and health. It collects vital data without gathering too much detail, making it suitable for production environments where minimal overhead is desired.<br><br>DEBUG level records most metrics, providing more detailed information about the system's operation. It's useful for development [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>INFO</td></tr>
-<tr><th>Valid Values:</th><td>[INFO, DEBUG, TRACE]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.sample.window.ms"></a><a id="consumerconfigs_metrics.sample.window.ms" href="#consumerconfigs_metrics.sample.window.ms">metrics.sample.window.ms</a></h4>
-<p>The window of time a metrics sample is computed over.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="reconnect.backoff.max.ms"></a><a id="consumerconfigs_reconnect.backoff.max.ms" href="#consumerconfigs_reconnect.backoff.max.ms">reconnect.backoff.max.ms</a></h4>
-<p>The maximum amount of time in milliseconds to wait when reconnecting to a broker that has repeatedly failed to connect. If provided, the backoff per host will increase exponentially for each consecutive connection failure, up to this maximum. After calculating the backoff increase, 20% random jitter is added to avoid connection storms.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="reconnect.backoff.ms"></a><a id="consumerconfigs_reconnect.backoff.ms" href="#consumerconfigs_reconnect.backoff.ms">reconnect.backoff.ms</a></h4>
-<p>The base amount of time to wait before attempting to reconnect to a given host. This avoids repeatedly connecting to a host in a tight loop. This backoff applies to all connection attempts by the client to a broker. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>reconnect.backoff.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>50</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="retry.backoff.max.ms"></a><a id="consumerconfigs_retry.backoff.max.ms" href="#consumerconfigs_retry.backoff.max.ms">retry.backoff.max.ms</a></h4>
-<p>The maximum amount of time in milliseconds to wait when retrying a request to the broker that has repeatedly failed. If provided, the backoff per client will increase exponentially for each failed request, up to this maximum. To prevent all clients from being synchronized upon retry, a randomized jitter with a factor of 0.2 will be applied to the backoff, resulting in the backoff falling within a range between 20% below and 20% above the computed value. If <code>retry.backoff.ms</code [...]
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="retry.backoff.ms"></a><a id="consumerconfigs_retry.backoff.ms" href="#consumerconfigs_retry.backoff.ms">retry.backoff.ms</a></h4>
-<p>The amount of time to wait before attempting to retry a failed request to a given topic partition. This avoids repeatedly sending requests in a tight loop under some failure scenarios. This value is the initial backoff value and will increase exponentially for each failed request, up to the <code>retry.backoff.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.kinit.cmd"></a><a id="consumerconfigs_sasl.kerberos.kinit.cmd" href="#consumerconfigs_sasl.kerberos.kinit.cmd">sasl.kerberos.kinit.cmd</a></h4>
-<p>Kerberos kinit command path.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>/usr/bin/kinit</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.min.time.before.relogin"></a><a id="consumerconfigs_sasl.kerberos.min.time.before.relogin" href="#consumerconfigs_sasl.kerberos.min.time.before.relogin">sasl.kerberos.min.time.before.relogin</a></h4>
-<p>Login thread sleep time between refresh attempts.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60000</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.ticket.renew.jitter"></a><a id="consumerconfigs_sasl.kerberos.ticket.renew.jitter" href="#consumerconfigs_sasl.kerberos.ticket.renew.jitter">sasl.kerberos.ticket.renew.jitter</a></h4>
-<p>Percentage of random jitter added to the renewal time.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.05</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.ticket.renew.window.factor"></a><a id="consumerconfigs_sasl.kerberos.ticket.renew.window.factor" href="#consumerconfigs_sasl.kerberos.ticket.renew.window.factor">sasl.kerberos.ticket.renew.window.factor</a></h4>
-<p>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.8</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.connect.timeout.ms"></a><a id="consumerconfigs_sasl.login.connect.timeout.ms" href="#consumerconfigs_sasl.login.connect.timeout.ms">sasl.login.connect.timeout.ms</a></h4>
-<p>The (optional) value in milliseconds for the external authentication provider connection timeout. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.read.timeout.ms"></a><a id="consumerconfigs_sasl.login.read.timeout.ms" href="#consumerconfigs_sasl.login.read.timeout.ms">sasl.login.read.timeout.ms</a></h4>
-<p>The (optional) value in milliseconds for the external authentication provider read timeout. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.buffer.seconds"></a><a id="consumerconfigs_sasl.login.refresh.buffer.seconds" href="#consumerconfigs_sasl.login.refresh.buffer.seconds">sasl.login.refresh.buffer.seconds</a></h4>
-<p>The amount of buffer time before credential expiration to maintain when refreshing a credential, in seconds. If a refresh would otherwise occur closer to expiration than the number of buffer seconds then the refresh will be moved up to maintain as much of the buffer time as possible. Legal values are between 0 and 3600 (1 hour); a default value of 300 (5 minutes) is used if no value is specified. This value and sasl.login.refresh.min.period.seconds are both ignored if their sum excee [...]
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.min.period.seconds"></a><a id="consumerconfigs_sasl.login.refresh.min.period.seconds" href="#consumerconfigs_sasl.login.refresh.min.period.seconds">sasl.login.refresh.min.period.seconds</a></h4>
-<p>The desired minimum time for the login refresh thread to wait before refreshing a credential, in seconds. Legal values are between 0 and 900 (15 minutes); a default value of 60 (1 minute) is used if no value is specified. This value and sasl.login.refresh.buffer.seconds are both ignored if their sum exceeds the remaining lifetime of a credential. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,900]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.window.factor"></a><a id="consumerconfigs_sasl.login.refresh.window.factor" href="#consumerconfigs_sasl.login.refresh.window.factor">sasl.login.refresh.window.factor</a></h4>
-<p>Login refresh thread will sleep until the specified window factor relative to the credential's lifetime has been reached, at which time it will try to refresh the credential. Legal values are between 0.5 (50%) and 1.0 (100%) inclusive; a default value of 0.8 (80%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.8</td></tr>
-<tr><th>Valid Values:</th><td>[0.5,...,1.0]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.window.jitter"></a><a id="consumerconfigs_sasl.login.refresh.window.jitter" href="#consumerconfigs_sasl.login.refresh.window.jitter">sasl.login.refresh.window.jitter</a></h4>
-<p>The maximum amount of random jitter relative to the credential's lifetime that is added to the login refresh thread's sleep time. Legal values are between 0 and 0.25 (25%) inclusive; a default value of 0.05 (5%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.05</td></tr>
-<tr><th>Valid Values:</th><td>[0.0,...,0.25]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.retry.backoff.max.ms"></a><a id="consumerconfigs_sasl.login.retry.backoff.max.ms" href="#consumerconfigs_sasl.login.retry.backoff.max.ms">sasl.login.retry.backoff.max.ms</a></h4>
-<p>The (optional) value in milliseconds for the maximum wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.retry.backoff.ms"></a><a id="consumerconfigs_sasl.login.retry.backoff.ms" href="#consumerconfigs_sasl.login.retry.backoff.ms">sasl.login.retry.backoff.ms</a></h4>
-<p>The (optional) value in milliseconds for the initial wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.exp.seconds"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.claim.exp.seconds" href="#consumerconfigs_sasl.oauthbearer.assertion.claim.exp.seconds">sasl.oauthbearer.assertion.claim.exp.seconds</a></h4>
-<p><p>The number of seconds <em>in the future</em> for which the JWT is valid. The value is used to determine the JWT <code>exp</code> (Expiration) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>exp</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> exp = x + y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbear [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,86400]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.nbf.seconds"></a><a id="consumerconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds" href="#consumerconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds">sasl.oauthbearer.assertion.claim.nbf.seconds</a></h4>
-<p><p>The number of seconds <em>in the past</em> from which the JWT is valid. The value is used to determine the JWT <code>nbf</code> (Not Before) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>nbf</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> nbf = x - y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbeare [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.clock.skew.seconds"></a><a id="consumerconfigs_sasl.oauthbearer.clock.skew.seconds" href="#consumerconfigs_sasl.oauthbearer.clock.skew.seconds">sasl.oauthbearer.clock.skew.seconds</a></h4>
-<p>The (optional) value in seconds to allow for differences between the time of the OAuth/OIDC identity provider and the broker.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.expected.audience"></a><a id="consumerconfigs_sasl.oauthbearer.expected.audience" href="#consumerconfigs_sasl.oauthbearer.expected.audience">sasl.oauthbearer.expected.audience</a></h4>
-<p>The (optional) comma-delimited setting for the broker to use to verify that the JWT was issued for one of the expected audiences. The JWT will be inspected for the standard OAuth "aud" claim and if this value is set, the broker will match the value from JWT's "aud" claim to see if there is an exact match. If there is no match, the broker will reject the JWT and authentication will fail.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.expected.issuer"></a><a id="consumerconfigs_sasl.oauthbearer.expected.issuer" href="#consumerconfigs_sasl.oauthbearer.expected.issuer">sasl.oauthbearer.expected.issuer</a></h4>
-<p>The (optional) setting for the broker to use to verify that the JWT was created by the expected issuer. The JWT will be inspected for the standard OAuth "iss" claim and if this value is set, the broker will match it exactly against what is in the JWT's "iss" claim. If there is no match, the broker will reject the JWT and authentication will fail.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.header.urlencode"></a><a id="consumerconfigs_sasl.oauthbearer.header.urlencode" href="#consumerconfigs_sasl.oauthbearer.header.urlencode">sasl.oauthbearer.header.urlencode</a></h4>
-<p>The (optional) setting to enable the OAuth client to URL-encode the client_id and client_secret in the authorization header in accordance with RFC6749, see <a href="https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1">here</a> for more details. The default value is set to 'false' for backward compatibility</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.refresh.ms"></a><a id="consumerconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms" href="#consumerconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms">sasl.oauthbearer.jwks.endpoint.refresh.ms</a></h4>
-<p>The (optional) value in milliseconds for the broker to wait between refreshing its JWKS (JSON Web Key Set) cache that contains the keys to verify the signature of the JWT.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms"></a><a id="consumerconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms" href="#consumerconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms</a></h4>
-<p>The (optional) value in milliseconds for the maximum wait between attempts to retrieve the JWKS (JSON Web Key Set) from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.ms"></a><a id="consumerconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms" href="#consumerconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.ms</a></h4>
-<p>The (optional) value in milliseconds for the initial wait between JWKS (JSON Web Key Set) retrieval attempts from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.scope.claim.name"></a><a id="consumerconfigs_sasl.oauthbearer.scope.claim.name" href="#consumerconfigs_sasl.oauthbearer.scope.claim.name">sasl.oauthbearer.scope.claim.name</a></h4>
-<p>The OAuth claim for the scope is often named "scope", but this (optional) setting can provide a different name to use for the scope included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>scope</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.sub.claim.name"></a><a id="consumerconfigs_sasl.oauthbearer.sub.claim.name" href="#consumerconfigs_sasl.oauthbearer.sub.claim.name">sasl.oauthbearer.sub.claim.name</a></h4>
-<p>The OAuth claim for the subject is often named "sub", but this (optional) setting can provide a different name to use for the subject included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>sub</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="security.providers"></a><a id="consumerconfigs_security.providers" href="#consumerconfigs_security.providers">security.providers</a></h4>
-<p>A list of configurable creator classes each returning a provider implementing security algorithms. These classes should implement the <code>org.apache.kafka.common.security.auth.SecurityProviderCreator</code> interface.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.cipher.suites"></a><a id="consumerconfigs_ssl.cipher.suites" href="#consumerconfigs_ssl.cipher.suites">ssl.cipher.suites</a></h4>
-<p>A list of cipher suites. This is a named combination of authentication, encryption, MAC and key exchange algorithm used to negotiate the security settings for a network connection using TLS or SSL network protocol. By default all the available cipher suites are supported.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.endpoint.identification.algorithm"></a><a id="consumerconfigs_ssl.endpoint.identification.algorithm" href="#consumerconfigs_ssl.endpoint.identification.algorithm">ssl.endpoint.identification.algorithm</a></h4>
-<p>The endpoint identification algorithm to validate server hostname using server certificate. </p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>https</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.engine.factory.class"></a><a id="consumerconfigs_ssl.engine.factory.class" href="#consumerconfigs_ssl.engine.factory.class">ssl.engine.factory.class</a></h4>
-<p>The class of type org.apache.kafka.common.security.auth.SslEngineFactory to provide SSLEngine objects. Default value is org.apache.kafka.common.security.ssl.DefaultSslEngineFactory. Alternatively, setting this to org.apache.kafka.common.security.ssl.CommonNameLoggingSslEngineFactory will log the common name of expired SSL certificates used by clients to authenticate at any of the brokers with log level INFO. Note that this will cause a tiny delay during establishment of new connection [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keymanager.algorithm"></a><a id="consumerconfigs_ssl.keymanager.algorithm" href="#consumerconfigs_ssl.keymanager.algorithm">ssl.keymanager.algorithm</a></h4>
-<p>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>SunX509</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.secure.random.implementation"></a><a id="consumerconfigs_ssl.secure.random.implementation" href="#consumerconfigs_ssl.secure.random.implementation">ssl.secure.random.implementation</a></h4>
-<p>The SecureRandom PRNG implementation to use for SSL cryptography operations. </p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.trustmanager.algorithm"></a><a id="consumerconfigs_ssl.trustmanager.algorithm" href="#consumerconfigs_ssl.trustmanager.algorithm">ssl.trustmanager.algorithm</a></h4>
-<p>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>PKIX</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-</ul>
-
diff --git a/content/en/43/generated/consumer_metrics.html b/content/en/43/generated/consumer_metrics.html
index 25e3750143..e69de29bb2 100644
--- a/content/en/43/generated/consumer_metrics.html
+++ b/content/en/43/generated/consumer_metrics.html
@@ -1,153 +0,0 @@
-<table class="data-table">
-<tbody>
-<tr>
-<th>Metric/Attribute name</th>
-<th>Description</th>
-<th>Mbean name</th>
-</tr>
-<tr>
-<td>bytes-consumed-rate</td>
-<td>The average number of bytes consumed per second</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>bytes-consumed-total</td>
-<td>The total number of bytes consumed</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>fetch-latency-avg</td>
-<td>The average time taken for a fetch request.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>fetch-latency-max</td>
-<td>The max time taken for any fetch request.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>fetch-rate</td>
-<td>The number of fetch requests per second.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>fetch-size-avg</td>
-<td>The average number of bytes fetched per request</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>fetch-size-max</td>
-<td>The maximum number of bytes fetched per request</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>fetch-throttle-time-avg</td>
-<td>The average throttle time in ms</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>fetch-throttle-time-max</td>
-<td>The maximum throttle time in ms</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>fetch-total</td>
-<td>The total number of fetch requests.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-consumed-rate</td>
-<td>The average number of records consumed per second</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-consumed-total</td>
-<td>The total number of records consumed</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-lag-max</td>
-<td>The maximum lag in terms of number of records for any partition in this window. NOTE: This is based on current offset and not committed offset</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-lead-min</td>
-<td>The minimum lead in terms of number of records for any partition in this window</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-per-request-avg</td>
-<td>The average number of records in each request</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>bytes-consumed-rate</td>
-<td>The average number of bytes consumed per second for a topic. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}",topic="{topic}"</td>
-</tr>
-<tr>
-<td>bytes-consumed-total</td>
-<td>The total number of bytes consumed for a topic. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}",topic="{topic}"</td>
-</tr>
-<tr>
-<td>fetch-size-avg</td>
-<td>The average number of bytes fetched per request for a topic. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}",topic="{topic}"</td>
-</tr>
-<tr>
-<td>fetch-size-max</td>
-<td>The maximum number of bytes fetched per request for a topic. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}",topic="{topic}"</td>
-</tr>
-<tr>
-<td>records-consumed-rate</td>
-<td>The average number of records consumed per second for a topic. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}",topic="{topic}"</td>
-</tr>
-<tr>
-<td>records-consumed-total</td>
-<td>The total number of records consumed for a topic. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}",topic="{topic}"</td>
-</tr>
-<tr>
-<td>records-per-request-avg</td>
-<td>The average number of records in each request for a topic. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,client-id="{client-id}",topic="{topic}"</td>
-</tr>
-<tr>
-<td>preferred-read-replica</td>
-<td>The current read replica for the partition, or -1 if reading from leader. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,partition="{partition}",topic="{topic}",client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-lag</td>
-<td>The latest lag of the partition. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,partition="{partition}",topic="{topic}",client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-lag-avg</td>
-<td>The average lag of the partition. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,partition="{partition}",topic="{topic}",client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-lag-max</td>
-<td>The max lag of the partition. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,partition="{partition}",topic="{topic}",client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-lead</td>
-<td>The latest lead of the partition. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,partition="{partition}",topic="{topic}",client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-lead-avg</td>
-<td>The average lead of the partition. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,partition="{partition}",topic="{topic}",client-id="{client-id}"</td>
-</tr>
-<tr>
-<td>records-lead-min</td>
-<td>The min lead of the partition. Note: For topic names with periods (.), an additional metric with underscores is emitted. However, the periods replaced metric is deprecated. Please use the metric with actual topic name instead.</td>
-<td>kafka.consumer:type=consumer-fetch-manager-metrics,partition="{partition}",topic="{topic}",client-id="{client-id}"</td>
-</tr>
-</tbody></table>
diff --git a/content/en/43/generated/group_config.html b/content/en/43/generated/group_config.html
index 3a19874a69..e69de29bb2 100644
--- a/content/en/43/generated/group_config.html
+++ b/content/en/43/generated/group_config.html
@@ -1,173 +0,0 @@
-<ul class="config-list">
-<li>
-<h4><a id="consumer.assignment.interval.ms"></a><a id="groupconfigs_consumer.assignment.interval.ms" href="#groupconfigs_consumer.assignment.interval.ms">consumer.assignment.interval.ms</a></h4>
-<p>The interval between assignment updates for a consumer group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="consumer.heartbeat.interval.ms"></a><a id="groupconfigs_consumer.heartbeat.interval.ms" href="#groupconfigs_consumer.heartbeat.interval.ms">consumer.heartbeat.interval.ms</a></h4>
-<p>The heartbeat interval given to the members of a consumer group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="consumer.session.timeout.ms"></a><a id="groupconfigs_consumer.session.timeout.ms" href="#groupconfigs_consumer.session.timeout.ms">consumer.session.timeout.ms</a></h4>
-<p>The timeout to detect client failures when using the consumer group protocol.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.assignment.interval.ms"></a><a id="groupconfigs_share.assignment.interval.ms" href="#groupconfigs_share.assignment.interval.ms">share.assignment.interval.ms</a></h4>
-<p>The interval between assignment updates for a share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.auto.offset.reset"></a><a id="groupconfigs_share.auto.offset.reset" href="#groupconfigs_share.auto.offset.reset">share.auto.offset.reset</a></h4>
-<p>The strategy to initialize the share-partition start offset. <ul><li>earliest: automatically reset the offset to the earliest offset</li><li>latest: automatically reset the offset to the latest offset</li><li>by_duration:<duration>: automatically reset the offset to a configured duration from the current timestamp. <duration> must be specified in ISO8601 format (PnDTnHnMn.nS). Negative duration is not allowed.</li><li>anything else: throw exception to the share consumer.</ [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>latest</td></tr>
-<tr><th>Valid Values:</th><td>[latest, earliest, by_duration:PnDTnHnMn.nS]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.delivery.count.limit"></a><a id="groupconfigs_share.delivery.count.limit" href="#groupconfigs_share.delivery.count.limit">share.delivery.count.limit</a></h4>
-<p>The maximum number of delivery attempts for a record delivered to a share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5</td></tr>
-<tr><th>Valid Values:</th><td>[2,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.heartbeat.interval.ms"></a><a id="groupconfigs_share.heartbeat.interval.ms" href="#groupconfigs_share.heartbeat.interval.ms">share.heartbeat.interval.ms</a></h4>
-<p>The heartbeat interval given to the members of a share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.isolation.level"></a><a id="groupconfigs_share.isolation.level" href="#groupconfigs_share.isolation.level">share.isolation.level</a></h4>
-<p>Controls how to read records written transactionally. If set to "read_committed", the share group will only deliver transactional records which have been committed. If set to "read_uncommitted", the share group will return all messages, even transactional messages which have been aborted. Non-transactional records will be returned unconditionally in either mode.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>read_uncommitted</td></tr>
-<tr><th>Valid Values:</th><td>[read_committed, read_uncommitted]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.partition.max.record.locks"></a><a id="groupconfigs_share.partition.max.record.locks" href="#groupconfigs_share.partition.max.record.locks">share.partition.max.record.locks</a></h4>
-<p>Share-group record lock limit per share-partition.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2000</td></tr>
-<tr><th>Valid Values:</th><td>[100,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.record.lock.duration.ms"></a><a id="groupconfigs_share.record.lock.duration.ms" href="#groupconfigs_share.record.lock.duration.ms">share.record.lock.duration.ms</a></h4>
-<p>The record acquisition lock duration in milliseconds for share groups.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1000,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.renew.acknowledge.enable"></a><a id="groupconfigs_share.renew.acknowledge.enable" href="#groupconfigs_share.renew.acknowledge.enable">share.renew.acknowledge.enable</a></h4>
-<p>Whether the renew acknowledge type is enabled for the share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.session.timeout.ms"></a><a id="groupconfigs_share.session.timeout.ms" href="#groupconfigs_share.session.timeout.ms">share.session.timeout.ms</a></h4>
-<p>The timeout to detect client failures when using the share group protocol.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="streams.assignment.interval.ms"></a><a id="groupconfigs_streams.assignment.interval.ms" href="#groupconfigs_streams.assignment.interval.ms">streams.assignment.interval.ms</a></h4>
-<p>The interval between assignment updates for a streams group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="streams.heartbeat.interval.ms"></a><a id="groupconfigs_streams.heartbeat.interval.ms" href="#groupconfigs_streams.heartbeat.interval.ms">streams.heartbeat.interval.ms</a></h4>
-<p>The heartbeat interval given to the members.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="streams.initial.rebalance.delay.ms"></a><a id="groupconfigs_streams.initial.rebalance.delay.ms" href="#groupconfigs_streams.initial.rebalance.delay.ms">streams.initial.rebalance.delay.ms</a></h4>
-<p>The amount of time the group coordinator will wait for more streams clients to join a new group before performing the first rebalance. A longer delay means potentially fewer rebalances.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>3000 (3 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="streams.num.standby.replicas"></a><a id="groupconfigs_streams.num.standby.replicas" href="#groupconfigs_streams.num.standby.replicas">streams.num.standby.replicas</a></h4>
-<p>The number of standby replicas for each task.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="streams.session.timeout.ms"></a><a id="groupconfigs_streams.session.timeout.ms" href="#groupconfigs_streams.session.timeout.ms">streams.session.timeout.ms</a></h4>
-<p>The timeout to detect client failures when using the streams group protocol.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
diff --git a/content/en/43/generated/kafka_config.html b/content/en/43/generated/kafka_config.html
index fd66ffb9a1..e69de29bb2 100644
--- a/content/en/43/generated/kafka_config.html
+++ b/content/en/43/generated/kafka_config.html
@@ -1,3776 +0,0 @@
-<ul class="config-list">
-<li>
-<h4><a id="controller.listener.names"></a><a id="brokerconfigs_controller.listener.names" href="#brokerconfigs_controller.listener.names">controller.listener.names</a></h4>
-<p>A comma-separated list of the names of the listeners used by the controller. This is required when communicating with the controller quorum, the broker will always use the first listener in this list.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="node.id"></a><a id="brokerconfigs_node.id" href="#brokerconfigs_node.id">node.id</a></h4>
-<p>The node ID associated with the roles this process is playing when <code>process.roles</code> is non-empty. This is required configuration when running in KRaft mode.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="process.roles"></a><a id="brokerconfigs_process.roles" href="#brokerconfigs_process.roles">process.roles</a></h4>
-<p>The roles that this process plays: 'broker', 'controller', or 'broker,controller' if it is both. </p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>[broker, controller]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="add.partitions.to.txn.retry.backoff.max.ms"></a><a id="brokerconfigs_add.partitions.to.txn.retry.backoff.max.ms" href="#brokerconfigs_add.partitions.to.txn.retry.backoff.max.ms">add.partitions.to.txn.retry.backoff.max.ms</a></h4>
-<p>The maximum allowed timeout for adding partitions to transactions on the server side. It only applies to the actual add partition operations, not the verification. It will not be effective if it is larger than request.timeout.ms</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="add.partitions.to.txn.retry.backoff.ms"></a><a id="brokerconfigs_add.partitions.to.txn.retry.backoff.ms" href="#brokerconfigs_add.partitions.to.txn.retry.backoff.ms">add.partitions.to.txn.retry.backoff.ms</a></h4>
-<p>The server-side retry backoff when the server attemptsto add the partition to the transaction</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>20</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="advertised.listeners"></a><a id="brokerconfigs_advertised.listeners" href="#brokerconfigs_advertised.listeners">advertised.listeners</a></h4>
-<p>Specifies the listener addresses that the Kafka brokers will advertise to clients and other brokers. The config is useful where the actual listener configuration <code>listeners</code> does not represent the addresses that clients should use to connect, such as in cloud environments. The addresses are published to and managed by the controller, the brokers pull these data from the controller as needed. In IaaS environments, this may need to be different from the interface to which the [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="auto.create.topics.enable"></a><a id="brokerconfigs_auto.create.topics.enable" href="#brokerconfigs_auto.create.topics.enable">auto.create.topics.enable</a></h4>
-<p>Enable auto creation of topic on the server.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="auto.leader.rebalance.enable"></a><a id="brokerconfigs_auto.leader.rebalance.enable" href="#brokerconfigs_auto.leader.rebalance.enable">auto.leader.rebalance.enable</a></h4>
-<p>Enables auto leader balancing. A background thread checks the distribution of partition leaders at regular intervals, configurable by leader.imbalance.check.interval.seconds. If the leader is imbalanced, leader rebalance to the preferred leader for partitions is triggered.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="background.threads"></a><a id="brokerconfigs_background.threads" href="#brokerconfigs_background.threads">background.threads</a></h4>
-<p>The number of threads to use for various background processing tasks</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="broker.id"></a><a id="brokerconfigs_broker.id" href="#brokerconfigs_broker.id">broker.id</a></h4>
-<p>The broker id for this server.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>-1</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="compression.type"></a><a id="brokerconfigs_compression.type" href="#brokerconfigs_compression.type">compression.type</a></h4>
-<p>Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>producer</td></tr>
-<tr><th>Valid Values:</th><td>[uncompressed, zstd, lz4, snappy, gzip, producer]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.bootstrap.servers"></a><a id="brokerconfigs_controller.quorum.bootstrap.servers" href="#brokerconfigs_controller.quorum.bootstrap.servers">controller.quorum.bootstrap.servers</a></h4>
-<p>List of endpoints to use for bootstrapping the cluster metadata. The endpoints are specified in comma-separated list of <code>{host}:{port}</code> entries. For example: <code>localhost:9092,localhost:9093,localhost:9094</code>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td>non-empty list</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.election.backoff.max.ms"></a><a id="brokerconfigs_controller.quorum.election.backoff.max.ms" href="#brokerconfigs_controller.quorum.election.backoff.max.ms">controller.quorum.election.backoff.max.ms</a></h4>
-<p>Maximum time in milliseconds before starting new elections. This is used in the binary exponential backoff mechanism that helps prevent gridlocked elections</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.election.timeout.ms"></a><a id="brokerconfigs_controller.quorum.election.timeout.ms" href="#brokerconfigs_controller.quorum.election.timeout.ms">controller.quorum.election.timeout.ms</a></h4>
-<p>Maximum time in milliseconds to wait without being able to fetch from the leader before triggering a new election</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.fetch.timeout.ms"></a><a id="brokerconfigs_controller.quorum.fetch.timeout.ms" href="#brokerconfigs_controller.quorum.fetch.timeout.ms">controller.quorum.fetch.timeout.ms</a></h4>
-<p>Maximum time without a successful fetch from the current leader before becoming a candidate and triggering an election for voters; Maximum time a leader can go without receiving valid fetch or fetchSnapshot request from a majority of the quorum before resigning.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2000 (2 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.voters"></a><a id="brokerconfigs_controller.quorum.voters" href="#brokerconfigs_controller.quorum.voters">controller.quorum.voters</a></h4>
-<p>Map of id/endpoint information for the set of voters in a comma-separated list of <code>{id}@{host}:{port}</code> entries. This is the old way of defining membership for controller quorums and should NOT be set if using dynamic quorums. Instead, controller.quorum.bootstrap.servers should be set,and the voter set is determined by the --standalone or --initial-controllers flags when formatting.For example: <code>1@localhost:9092,2@localhost:9093,3@localhost:9094</code></p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td>non-empty list</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="delete.topic.enable"></a><a id="brokerconfigs_delete.topic.enable" href="#brokerconfigs_delete.topic.enable">delete.topic.enable</a></h4>
-<p>When set to true, topics can be deleted by the admin client. When set to false, deletion requests will be explicitly rejected by the broker.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="early.start.listeners"></a><a id="brokerconfigs_early.start.listeners" href="#brokerconfigs_early.start.listeners">early.start.listeners</a></h4>
-<p>A comma-separated list of listener names which may be started before the authorizer has finished initialization. This is useful when the authorizer is dependent on the cluster itself for bootstrapping, as is the case for the StandardAuthorizer (which stores ACLs in the metadata log.) By default, all listeners included in controller.listener.names will also be early start listeners. A listener should not appear in this list if it accepts external traffic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.coordinator.background.threads"></a><a id="brokerconfigs_group.coordinator.background.threads" href="#brokerconfigs_group.coordinator.background.threads">group.coordinator.background.threads</a></h4>
-<p>The number of threads used by the group coordinator for processing background tasks (e.g. updating regular expression subscriptions and offloaded assignments).</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.coordinator.threads"></a><a id="brokerconfigs_group.coordinator.threads" href="#brokerconfigs_group.coordinator.threads">group.coordinator.threads</a></h4>
-<p>The number of threads used by the group coordinator for processing requests.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>4</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="leader.imbalance.check.interval.seconds"></a><a id="brokerconfigs_leader.imbalance.check.interval.seconds" href="#brokerconfigs_leader.imbalance.check.interval.seconds">leader.imbalance.check.interval.seconds</a></h4>
-<p>The frequency with which the partition rebalance check is triggered by the controller</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="listeners"></a><a id="brokerconfigs_listeners" href="#brokerconfigs_listeners">listeners</a></h4>
-<p>Listener List - Comma-separated list of URIs we will listen on and the listener names. If the listener name is not a security protocol, <code>listener.security.protocol.map</code> must also be set.<br> Listener names and port numbers must be unique unless one listener is an IPv4 address and the other listener is an IPv6 address (for the same port).<br> Specify hostname as 0.0.0.0 to bind to all interfaces.<br> Leave hostname empty to bind to default interface.<br> Examples of legal li [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>PLAINTEXT://:9092</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.dir"></a><a id="brokerconfigs_log.dir" href="#brokerconfigs_log.dir">log.dir</a></h4>
-<p>A comma-separated list of the directories where the log data is stored. (supplemental to log.dirs property)</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>/tmp/kafka-logs</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.dirs"></a><a id="brokerconfigs_log.dirs" href="#brokerconfigs_log.dirs">log.dirs</a></h4>
-<p>A comma-separated list of the directories where the log data is stored. If not set, the value in log.dir is used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.flush.interval.messages"></a><a id="brokerconfigs_log.flush.interval.messages" href="#brokerconfigs_log.flush.interval.messages">log.flush.interval.messages</a></h4>
-<p>The number of messages accumulated on a log partition before messages are flushed to disk.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>9223372036854775807</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.flush.interval.ms"></a><a id="brokerconfigs_log.flush.interval.ms" href="#brokerconfigs_log.flush.interval.ms">log.flush.interval.ms</a></h4>
-<p>The maximum time in ms that a message in any topic is kept in memory before flushed to disk. If not set, the value in log.flush.scheduler.interval.ms is used</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.flush.offset.checkpoint.interval.ms"></a><a id="brokerconfigs_log.flush.offset.checkpoint.interval.ms" href="#brokerconfigs_log.flush.offset.checkpoint.interval.ms">log.flush.offset.checkpoint.interval.ms</a></h4>
-<p>The frequency with which we update the persistent record of the last flush which acts as the log recovery point.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.flush.scheduler.interval.ms"></a><a id="brokerconfigs_log.flush.scheduler.interval.ms" href="#brokerconfigs_log.flush.scheduler.interval.ms">log.flush.scheduler.interval.ms</a></h4>
-<p>The frequency in ms that the log flusher checks whether any log needs to be flushed to disk</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>9223372036854775807</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.flush.start.offset.checkpoint.interval.ms"></a><a id="brokerconfigs_log.flush.start.offset.checkpoint.interval.ms" href="#brokerconfigs_log.flush.start.offset.checkpoint.interval.ms">log.flush.start.offset.checkpoint.interval.ms</a></h4>
-<p>The frequency with which we update the persistent record of log start offset</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.retention.bytes"></a><a id="brokerconfigs_log.retention.bytes" href="#brokerconfigs_log.retention.bytes">log.retention.bytes</a></h4>
-<p>The maximum size of the log before deleting it</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>-1</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.retention.hours"></a><a id="brokerconfigs_log.retention.hours" href="#brokerconfigs_log.retention.hours">log.retention.hours</a></h4>
-<p>The number of hours to keep a log file before deleting it (in hours), tertiary to log.retention.ms property</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>168</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.retention.minutes"></a><a id="brokerconfigs_log.retention.minutes" href="#brokerconfigs_log.retention.minutes">log.retention.minutes</a></h4>
-<p>The number of minutes to keep a log file before deleting it (in minutes), secondary to log.retention.ms property. If not set, the value in log.retention.hours is used</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.retention.ms"></a><a id="brokerconfigs_log.retention.ms" href="#brokerconfigs_log.retention.ms">log.retention.ms</a></h4>
-<p>The number of milliseconds to keep a log file before deleting it (in milliseconds), If not set, the value in log.retention.minutes is used. If set to -1, no time limit is applied.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.roll.hours"></a><a id="brokerconfigs_log.roll.hours" href="#brokerconfigs_log.roll.hours">log.roll.hours</a></h4>
-<p>The maximum time before a new log segment is rolled out (in hours), secondary to log.roll.ms property</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>168</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.roll.jitter.hours"></a><a id="brokerconfigs_log.roll.jitter.hours" href="#brokerconfigs_log.roll.jitter.hours">log.roll.jitter.hours</a></h4>
-<p>The maximum jitter to subtract from logRollTimeMillis (in hours), secondary to log.roll.jitter.ms property</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.roll.jitter.ms"></a><a id="brokerconfigs_log.roll.jitter.ms" href="#brokerconfigs_log.roll.jitter.ms">log.roll.jitter.ms</a></h4>
-<p>The maximum jitter to subtract from logRollTimeMillis (in milliseconds). If not set, the value in log.roll.jitter.hours is used</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.roll.ms"></a><a id="brokerconfigs_log.roll.ms" href="#brokerconfigs_log.roll.ms">log.roll.ms</a></h4>
-<p>The maximum time before a new log segment is rolled out (in milliseconds). If not set, the value in log.roll.hours is used</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.segment.bytes"></a><a id="brokerconfigs_log.segment.bytes" href="#brokerconfigs_log.segment.bytes">log.segment.bytes</a></h4>
-<p>The maximum size of a single log file</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1073741824 (1 gibibyte)</td></tr>
-<tr><th>Valid Values:</th><td>[1048576,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.segment.delete.delay.ms"></a><a id="brokerconfigs_log.segment.delete.delay.ms" href="#brokerconfigs_log.segment.delete.delay.ms">log.segment.delete.delay.ms</a></h4>
-<p>The amount of time to wait before deleting a file from the filesystem. If the value is 0 and there is no file to delete, the system will wait 1 millisecond. Low value will cause busy waiting</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="message.max.bytes"></a><a id="brokerconfigs_message.max.bytes" href="#brokerconfigs_message.max.bytes">message.max.bytes</a></h4>
-<p>The largest record batch size allowed by Kafka (after compression if compression is enabled).This can be set per topic with the topic level <code>max.message.bytes</code> config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1048588</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.log.dir"></a><a id="brokerconfigs_metadata.log.dir" href="#brokerconfigs_metadata.log.dir">metadata.log.dir</a></h4>
-<p>This configuration determines where we put the metadata log. If it is not set, the metadata log is placed in the first log directory from log.dirs.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.log.max.record.bytes.between.snapshots"></a><a id="brokerconfigs_metadata.log.max.record.bytes.between.snapshots" href="#brokerconfigs_metadata.log.max.record.bytes.between.snapshots">metadata.log.max.record.bytes.between.snapshots</a></h4>
-<p>This is the maximum number of bytes in the log between the latest snapshot and the high-watermark needed before generating a new snapshot. The default value is 20971520. To generate snapshots based on the time elapsed, see the <code>metadata.log.max.snapshot.interval.ms</code> configuration. The Kafka node will generate a snapshot when either the maximum time interval is reached or the maximum bytes limit is reached.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>20971520</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.log.max.snapshot.interval.ms"></a><a id="brokerconfigs_metadata.log.max.snapshot.interval.ms" href="#brokerconfigs_metadata.log.max.snapshot.interval.ms">metadata.log.max.snapshot.interval.ms</a></h4>
-<p>This is the maximum number of milliseconds to wait to generate a snapshot if there are committed records in the log that are not included in the latest snapshot. A value of zero disables time based snapshot generation. The default value is 3600000. To generate snapshots based on the number of metadata bytes, see the <code>metadata.log.max.record.bytes.between.snapshots</code> configuration. The Kafka node will generate a snapshot when either the maximum time interval is reached or the [...]
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.log.segment.bytes"></a><a id="brokerconfigs_metadata.log.segment.bytes" href="#brokerconfigs_metadata.log.segment.bytes">metadata.log.segment.bytes</a></h4>
-<p>The maximum size of a single metadata log file.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1073741824 (1 gibibyte)</td></tr>
-<tr><th>Valid Values:</th><td>[8388608,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.log.segment.ms"></a><a id="brokerconfigs_metadata.log.segment.ms" href="#brokerconfigs_metadata.log.segment.ms">metadata.log.segment.ms</a></h4>
-<p>The maximum time before a new metadata log file is rolled out (in milliseconds).</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>604800000 (7 days)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.max.retention.bytes"></a><a id="brokerconfigs_metadata.max.retention.bytes" href="#brokerconfigs_metadata.max.retention.bytes">metadata.max.retention.bytes</a></h4>
-<p>The maximum combined size of the metadata log and snapshots before deleting old snapshots and log files. Since at least one snapshot must exist before any logs can be deleted, this is a soft limit.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>104857600 (100 mebibytes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.max.retention.ms"></a><a id="brokerconfigs_metadata.max.retention.ms" href="#brokerconfigs_metadata.max.retention.ms">metadata.max.retention.ms</a></h4>
-<p>The number of milliseconds to keep a metadata log file or snapshot before deleting it. Since at least one snapshot must exist before any logs can be deleted, this is a soft limit.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>604800000 (7 days)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="min.insync.replicas"></a><a id="brokerconfigs_min.insync.replicas" href="#brokerconfigs_min.insync.replicas">min.insync.replicas</a></h4>
-<p>Specifies the <i>minimum</i> number of in-sync replicas (including the leader) required for a write to succeed when a producer sets <code>acks</code> to "all" (or "-1"). In the <code>acks=all</code> case, every in-sync replica must acknowledge a write for it to be considered successful. E.g., if a topic has <code>replication.factor</code> of 3 and the ISR set includes all three replicas, then all three replicas must acknowledge an <code>acks=all</code> write for it to succeed, even if [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="num.io.threads"></a><a id="brokerconfigs_num.io.threads" href="#brokerconfigs_num.io.threads">num.io.threads</a></h4>
-<p>The number of threads that the server uses for processing requests, which may include disk I/O</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>8</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="num.network.threads"></a><a id="brokerconfigs_num.network.threads" href="#brokerconfigs_num.network.threads">num.network.threads</a></h4>
-<p>The number of threads that the server uses for receiving requests from the network and sending responses to the network. Noted: each listener (except for controller listener) creates its own thread pool.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="num.recovery.threads.per.data.dir"></a><a id="brokerconfigs_num.recovery.threads.per.data.dir" href="#brokerconfigs_num.recovery.threads.per.data.dir">num.recovery.threads.per.data.dir</a></h4>
-<p>The number of threads per data directory to be used for log recovery at startup and flushing at shutdown</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="num.replica.alter.log.dirs.threads"></a><a id="brokerconfigs_num.replica.alter.log.dirs.threads" href="#brokerconfigs_num.replica.alter.log.dirs.threads">num.replica.alter.log.dirs.threads</a></h4>
-<p>The number of threads that can move replicas between log directories, which may include disk I/O. The default value is equal to the number of directories specified in the <code>log.dir</code> or <code>log.dirs</code> configuration property.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="num.replica.fetchers"></a><a id="brokerconfigs_num.replica.fetchers" href="#brokerconfigs_num.replica.fetchers">num.replica.fetchers</a></h4>
-<p>Number of fetcher threads used to replicate records from each source broker. The total number of fetchers on each broker is bound by <code>num.replica.fetchers</code> multiplied by the number of brokers in the cluster.Increasing this value can increase the degree of I/O parallelism in the follower and leader broker at the cost of higher CPU and memory utilization.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offset.metadata.max.bytes"></a><a id="brokerconfigs_offset.metadata.max.bytes" href="#brokerconfigs_offset.metadata.max.bytes">offset.metadata.max.bytes</a></h4>
-<p>The maximum size for a metadata entry associated with an offset commit.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>4096 (4 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offsets.commit.timeout.ms"></a><a id="brokerconfigs_offsets.commit.timeout.ms" href="#brokerconfigs_offsets.commit.timeout.ms">offsets.commit.timeout.ms</a></h4>
-<p>Offset commit will be delayed until all replicas for the offsets topic receive the commit or this timeout is reached. This is similar to the producer request timeout. This is applied to all the writes made by the coordinator.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offsets.load.buffer.size"></a><a id="brokerconfigs_offsets.load.buffer.size" href="#brokerconfigs_offsets.load.buffer.size">offsets.load.buffer.size</a></h4>
-<p>Batch size for reading from the offsets segments when loading group metadata into the cache (soft-limit, overridden if records are too large).</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5242880</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offsets.retention.check.interval.ms"></a><a id="brokerconfigs_offsets.retention.check.interval.ms" href="#brokerconfigs_offsets.retention.check.interval.ms">offsets.retention.check.interval.ms</a></h4>
-<p>Frequency at which to check for stale offsets</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>600000 (10 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offsets.retention.minutes"></a><a id="brokerconfigs_offsets.retention.minutes" href="#brokerconfigs_offsets.retention.minutes">offsets.retention.minutes</a></h4>
-<p>For subscribed consumers, committed offset of a specific partition will be expired and discarded when 1) this retention period has elapsed after the consumer group loses all its consumers (i.e. becomes empty); 2) this retention period has elapsed since the last time an offset is committed for the partition and the group is no longer subscribed to the corresponding topic. For standalone consumers (using manual assignment), offsets will be expired after this retention period has elapsed [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10080</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offsets.topic.compression.codec"></a><a id="brokerconfigs_offsets.topic.compression.codec" href="#brokerconfigs_offsets.topic.compression.codec">offsets.topic.compression.codec</a></h4>
-<p>Compression codec for the offsets topic - compression may be used to achieve "atomic" commits.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offsets.topic.num.partitions"></a><a id="brokerconfigs_offsets.topic.num.partitions" href="#brokerconfigs_offsets.topic.num.partitions">offsets.topic.num.partitions</a></h4>
-<p>The number of partitions for the offset commit topic (should not change after deployment).</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>50</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offsets.topic.replication.factor"></a><a id="brokerconfigs_offsets.topic.replication.factor" href="#brokerconfigs_offsets.topic.replication.factor">offsets.topic.replication.factor</a></h4>
-<p>The replication factor for the offsets topic (set higher to ensure availability). Internal topic creation will fail until the cluster size meets this replication factor requirement.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offsets.topic.segment.bytes"></a><a id="brokerconfigs_offsets.topic.segment.bytes" href="#brokerconfigs_offsets.topic.segment.bytes">offsets.topic.segment.bytes</a></h4>
-<p>The offsets topic segment bytes should be kept relatively small in order to facilitate faster log compaction and cache loads.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>104857600 (100 mebibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="queued.max.requests"></a><a id="brokerconfigs_queued.max.requests" href="#brokerconfigs_queued.max.requests">queued.max.requests</a></h4>
-<p>The number of queued requests allowed for data-plane, before blocking the network threads</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>500</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.fetch.min.bytes"></a><a id="brokerconfigs_replica.fetch.min.bytes" href="#brokerconfigs_replica.fetch.min.bytes">replica.fetch.min.bytes</a></h4>
-<p>Minimum bytes expected for each fetch response. If not enough bytes, wait up to <code>replica.fetch.wait.max.ms</code> (broker config). Even if the total data available in the broker exceeds replica.fetch.min.bytes, the actual returned size may still be less than this value due to per-partition limits replica.fetch.max.bytes and max returned limits replica.fetch.response.max.bytes</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.fetch.wait.max.ms"></a><a id="brokerconfigs_replica.fetch.wait.max.ms" href="#brokerconfigs_replica.fetch.wait.max.ms">replica.fetch.wait.max.ms</a></h4>
-<p>The maximum wait time for each fetcher request issued by follower replicas. This value should always be less than the replica.lag.time.max.ms at all times to prevent frequent shrinking of ISR for low throughput topics</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>500</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.high.watermark.checkpoint.interval.ms"></a><a id="brokerconfigs_replica.high.watermark.checkpoint.interval.ms" href="#brokerconfigs_replica.high.watermark.checkpoint.interval.ms">replica.high.watermark.checkpoint.interval.ms</a></h4>
-<p>The frequency with which the high watermark is saved out to disk</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.lag.time.max.ms"></a><a id="brokerconfigs_replica.lag.time.max.ms" href="#brokerconfigs_replica.lag.time.max.ms">replica.lag.time.max.ms</a></h4>
-<p>If a follower hasn't sent any fetch requests or hasn't consumed up to the leader's log end offset for at least this time, the leader will remove the follower from ISR</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.socket.receive.buffer.bytes"></a><a id="brokerconfigs_replica.socket.receive.buffer.bytes" href="#brokerconfigs_replica.socket.receive.buffer.bytes">replica.socket.receive.buffer.bytes</a></h4>
-<p>The socket receive buffer for network requests to the leader for replicating data</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>65536 (64 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.socket.timeout.ms"></a><a id="brokerconfigs_replica.socket.timeout.ms" href="#brokerconfigs_replica.socket.timeout.ms">replica.socket.timeout.ms</a></h4>
-<p>The socket timeout for network requests. Its value should be at least replica.fetch.wait.max.ms</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="request.timeout.ms"></a><a id="brokerconfigs_request.timeout.ms" href="#brokerconfigs_request.timeout.ms">request.timeout.ms</a></h4>
-<p>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.mechanism.controller.protocol"></a><a id="brokerconfigs_sasl.mechanism.controller.protocol" href="#brokerconfigs_sasl.mechanism.controller.protocol">sasl.mechanism.controller.protocol</a></h4>
-<p>SASL mechanism used for communication with controllers. Default is GSSAPI.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>GSSAPI</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.load.buffer.size"></a><a id="brokerconfigs_share.coordinator.load.buffer.size" href="#brokerconfigs_share.coordinator.load.buffer.size">share.coordinator.load.buffer.size</a></h4>
-<p>Batch size for reading from the share-group state topic when loading state information into the cache (soft-limit, overridden if records are too large).</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5242880</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.state.topic.compression.codec"></a><a id="brokerconfigs_share.coordinator.state.topic.compression.codec" href="#brokerconfigs_share.coordinator.state.topic.compression.codec">share.coordinator.state.topic.compression.codec</a></h4>
-<p>Compression codec for the share-group state topic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.state.topic.min.isr"></a><a id="brokerconfigs_share.coordinator.state.topic.min.isr" href="#brokerconfigs_share.coordinator.state.topic.min.isr">share.coordinator.state.topic.min.isr</a></h4>
-<p>Overridden min.insync.replicas for the share-group state topic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.state.topic.num.partitions"></a><a id="brokerconfigs_share.coordinator.state.topic.num.partitions" href="#brokerconfigs_share.coordinator.state.topic.num.partitions">share.coordinator.state.topic.num.partitions</a></h4>
-<p>The number of partitions for the share-group state topic (should not change after deployment).</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>50</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.state.topic.replication.factor"></a><a id="brokerconfigs_share.coordinator.state.topic.replication.factor" href="#brokerconfigs_share.coordinator.state.topic.replication.factor">share.coordinator.state.topic.replication.factor</a></h4>
-<p>Replication factor for the share-group state topic. Topic creation will fail until the cluster size meets this replication factor requirement.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.state.topic.segment.bytes"></a><a id="brokerconfigs_share.coordinator.state.topic.segment.bytes" href="#brokerconfigs_share.coordinator.state.topic.segment.bytes">share.coordinator.state.topic.segment.bytes</a></h4>
-<p>The log segment size for the share-group state topic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>104857600 (100 mebibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.write.timeout.ms"></a><a id="brokerconfigs_share.coordinator.write.timeout.ms" href="#brokerconfigs_share.coordinator.write.timeout.ms">share.coordinator.write.timeout.ms</a></h4>
-<p>The duration in milliseconds that the share coordinator will wait for all replicas of the share-group state topic to receive a write.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.receive.buffer.bytes"></a><a id="brokerconfigs_socket.receive.buffer.bytes" href="#brokerconfigs_socket.receive.buffer.bytes">socket.receive.buffer.bytes</a></h4>
-<p>The SO_RCVBUF buffer of the socket server sockets. If the value is -1, the OS default will be used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>102400 (100 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.request.max.bytes"></a><a id="brokerconfigs_socket.request.max.bytes" href="#brokerconfigs_socket.request.max.bytes">socket.request.max.bytes</a></h4>
-<p>The maximum number of bytes in a socket request</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>104857600 (100 mebibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.send.buffer.bytes"></a><a id="brokerconfigs_socket.send.buffer.bytes" href="#brokerconfigs_socket.send.buffer.bytes">socket.send.buffer.bytes</a></h4>
-<p>The SO_SNDBUF buffer of the socket server sockets. If the value is -1, the OS default will be used.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>102400 (100 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transaction.max.timeout.ms"></a><a id="brokerconfigs_transaction.max.timeout.ms" href="#brokerconfigs_transaction.max.timeout.ms">transaction.max.timeout.ms</a></h4>
-<p>The maximum allowed timeout for transactions. If a client’s requested transaction time exceed this, then the broker will return an error in InitProducerIdRequest. This prevents a client from too large of a timeout, which can stall consumers reading from topics included in the transaction.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>900000 (15 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transaction.state.log.load.buffer.size"></a><a id="brokerconfigs_transaction.state.log.load.buffer.size" href="#brokerconfigs_transaction.state.log.load.buffer.size">transaction.state.log.load.buffer.size</a></h4>
-<p>Batch size for reading from the transaction log segments when loading producer ids and transactions into the cache (soft-limit, overridden if records are too large).</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5242880</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transaction.state.log.min.isr"></a><a id="brokerconfigs_transaction.state.log.min.isr" href="#brokerconfigs_transaction.state.log.min.isr">transaction.state.log.min.isr</a></h4>
-<p>The minimum number of replicas that must acknowledge a write to transaction topic in order to be considered successful.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transaction.state.log.num.partitions"></a><a id="brokerconfigs_transaction.state.log.num.partitions" href="#brokerconfigs_transaction.state.log.num.partitions">transaction.state.log.num.partitions</a></h4>
-<p>The number of partitions for the transaction topic (should not change after deployment).</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>50</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transaction.state.log.replication.factor"></a><a id="brokerconfigs_transaction.state.log.replication.factor" href="#brokerconfigs_transaction.state.log.replication.factor">transaction.state.log.replication.factor</a></h4>
-<p>The replication factor for the transaction topic (set higher to ensure availability). Internal topic creation will fail until the cluster size meets this replication factor requirement.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transaction.state.log.segment.bytes"></a><a id="brokerconfigs_transaction.state.log.segment.bytes" href="#brokerconfigs_transaction.state.log.segment.bytes">transaction.state.log.segment.bytes</a></h4>
-<p>The transaction topic segment bytes should be kept relatively small in order to facilitate faster log compaction and cache loads</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>104857600 (100 mebibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transactional.id.expiration.ms"></a><a id="brokerconfigs_transactional.id.expiration.ms" href="#brokerconfigs_transactional.id.expiration.ms">transactional.id.expiration.ms</a></h4>
-<p>The time in ms that the transaction coordinator will wait without receiving any transaction status updates for the current transaction before expiring its transactional id. Transactional IDs will not expire while a the transaction is still ongoing.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>604800000 (7 days)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="unclean.leader.election.enable"></a><a id="brokerconfigs_unclean.leader.election.enable" href="#brokerconfigs_unclean.leader.election.enable">unclean.leader.election.enable</a></h4>
-<p>Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss<p>Note: In KRaft mode, when enabling this config dynamically, it needs to wait for the unclean leader election thread to trigger election periodically (default is 5 minutes). Please run <code>kafka-leader-election.sh</code> with <code>unclean</code> option to trigger the unclean leader election immediately if needed.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="broker.heartbeat.interval.ms"></a><a id="brokerconfigs_broker.heartbeat.interval.ms" href="#brokerconfigs_broker.heartbeat.interval.ms">broker.heartbeat.interval.ms</a></h4>
-<p>The length of time in milliseconds between broker heartbeats.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2000 (2 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="broker.rack"></a><a id="brokerconfigs_broker.rack" href="#brokerconfigs_broker.rack">broker.rack</a></h4>
-<p>Rack of the broker. This will be used in rack aware replication assignment for fault tolerance. Examples: <code>RACK1</code>, <code>us-east-1d</code></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="broker.session.timeout.ms"></a><a id="brokerconfigs_broker.session.timeout.ms" href="#brokerconfigs_broker.session.timeout.ms">broker.session.timeout.ms</a></h4>
-<p>The length of time in milliseconds that a broker lease lasts if no heartbeats are made.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>9000 (9 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="compression.gzip.level"></a><a id="brokerconfigs_compression.gzip.level" href="#brokerconfigs_compression.gzip.level">compression.gzip.level</a></h4>
-<p>The compression level to use if compression.type is set to 'gzip'.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>-1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...,9] or -1</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="compression.lz4.level"></a><a id="brokerconfigs_compression.lz4.level" href="#brokerconfigs_compression.lz4.level">compression.lz4.level</a></h4>
-<p>The compression level to use if compression.type is set to 'lz4'.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>9</td></tr>
-<tr><th>Valid Values:</th><td>[1,...,17]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="compression.zstd.level"></a><a id="brokerconfigs_compression.zstd.level" href="#brokerconfigs_compression.zstd.level">compression.zstd.level</a></h4>
-<p>The compression level to use if compression.type is set to 'zstd'.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td>[-131072,...,22]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="connections.max.idle.ms"></a><a id="brokerconfigs_connections.max.idle.ms" href="#brokerconfigs_connections.max.idle.ms">connections.max.idle.ms</a></h4>
-<p>Idle connections timeout: the server socket processor threads close the connections that idle more than this</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>600000 (10 minutes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="connections.max.reauth.ms"></a><a id="brokerconfigs_connections.max.reauth.ms" href="#brokerconfigs_connections.max.reauth.ms">connections.max.reauth.ms</a></h4>
-<p>When explicitly set to a positive number (the default is 0, not a positive number), a session lifetime that will not exceed the configured value will be communicated to v2.2.0 or later clients when they authenticate. The broker will disconnect any such connection that is not re-authenticated within the session lifetime and that is then subsequently used for any purpose other than re-authentication. Configuration names can optionally be prefixed with listener prefix and SASL mechanism [...]
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controlled.shutdown.enable"></a><a id="brokerconfigs_controlled.shutdown.enable" href="#brokerconfigs_controlled.shutdown.enable">controlled.shutdown.enable</a></h4>
-<p>Enable controlled shutdown of the server.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.append.linger.ms"></a><a id="brokerconfigs_controller.quorum.append.linger.ms" href="#brokerconfigs_controller.quorum.append.linger.ms">controller.quorum.append.linger.ms</a></h4>
-<p>The duration in milliseconds that the leader will wait for writes to accumulate before flushing them to disk.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>25</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.request.timeout.ms"></a><a id="brokerconfigs_controller.quorum.request.timeout.ms" href="#brokerconfigs_controller.quorum.request.timeout.ms">controller.quorum.request.timeout.ms</a></h4>
-<p>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2000 (2 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.socket.timeout.ms"></a><a id="brokerconfigs_controller.socket.timeout.ms" href="#brokerconfigs_controller.socket.timeout.ms">controller.socket.timeout.ms</a></h4>
-<p>The socket timeout for controller-to-broker channels.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="cordoned.log.dirs"></a><a id="brokerconfigs_cordoned.log.dirs" href="#brokerconfigs_cordoned.log.dirs">cordoned.log.dirs</a></h4>
-<p>A comma-separated list of the directories that are cordoned. Entries in this list must be entries in log.dirs or log.dir configuration. This can also be set to * to cordon all log directories.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="default.replication.factor"></a><a id="brokerconfigs_default.replication.factor" href="#brokerconfigs_default.replication.factor">default.replication.factor</a></h4>
-<p>The default replication factor per topic. This configuration affects the following paths:<ul> <li>1. Auto topic creation</li> <li>2. Internal streams topic creation</li> <li>3. Topic creation via <code>AdminClient#createTopics</code> when the replication factor is set to -1</li></ul><p>For (1), the value from the broker configuration is used only when it is explicitly set. If it is not explicitly configured on the broker, the value from the controller configuration is used.<br/>For [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="delegation.token.expiry.time.ms"></a><a id="brokerconfigs_delegation.token.expiry.time.ms" href="#brokerconfigs_delegation.token.expiry.time.ms">delegation.token.expiry.time.ms</a></h4>
-<p>The token validity time in milliseconds before the token needs to be renewed. Default value 1 day.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>86400000 (1 day)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="delegation.token.max.lifetime.ms"></a><a id="brokerconfigs_delegation.token.max.lifetime.ms" href="#brokerconfigs_delegation.token.max.lifetime.ms">delegation.token.max.lifetime.ms</a></h4>
-<p>The token has a maximum lifetime beyond which it cannot be renewed anymore. Default value 7 days.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>604800000 (7 days)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="delegation.token.secret.key"></a><a id="brokerconfigs_delegation.token.secret.key" href="#brokerconfigs_delegation.token.secret.key">delegation.token.secret.key</a></h4>
-<p>Secret key to generate and verify delegation tokens. The same key must be configured across all the brokers. If using Kafka with KRaft, the key must also be set across all controllers. If the key is not set or set to empty string, brokers will disable the delegation token support.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="delete.records.purgatory.purge.interval.requests"></a><a id="brokerconfigs_delete.records.purgatory.purge.interval.requests" href="#brokerconfigs_delete.records.purgatory.purge.interval.requests">delete.records.purgatory.purge.interval.requests</a></h4>
-<p>The purge interval (in number of requests) of the delete records request purgatory</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="fetch.max.bytes"></a><a id="brokerconfigs_fetch.max.bytes" href="#brokerconfigs_fetch.max.bytes">fetch.max.bytes</a></h4>
-<p>The maximum number of bytes we will return for a fetch request. Must be at least 1024.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>57671680 (55 mebibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[1024,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="fetch.purgatory.purge.interval.requests"></a><a id="brokerconfigs_fetch.purgatory.purge.interval.requests" href="#brokerconfigs_fetch.purgatory.purge.interval.requests">fetch.purgatory.purge.interval.requests</a></h4>
-<p>The purge interval (in number of requests) of the fetch request purgatory</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="follower.fetch.last.tiered.offset.enable"></a><a id="brokerconfigs_follower.fetch.last.tiered.offset.enable" href="#brokerconfigs_follower.fetch.last.tiered.offset.enable">follower.fetch.last.tiered.offset.enable</a></h4>
-<p>When enabled, an empty follower skips offsets up to the last tiered offset and begins replication from the next offset.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="follower.replication.throttled.rate"></a><a id="brokerconfigs_follower.replication.throttled.rate" href="#brokerconfigs_follower.replication.throttled.rate">follower.replication.throttled.rate</a></h4>
-<p>A long representing the upper bound (bytes/sec) on replication traffic for followers enumerated in the property follower.replication.throttled.replicas (for each topic). This property can be only set dynamically. It is suggested that the limit be kept above 1MB/s for accurate behaviour.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>9223372036854775807</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.assignment.interval.ms"></a><a id="brokerconfigs_group.consumer.assignment.interval.ms" href="#brokerconfigs_group.consumer.assignment.interval.ms">group.consumer.assignment.interval.ms</a></h4>
-<p>The interval between assignment updates for a consumer group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.assignors"></a><a id="brokerconfigs_group.consumer.assignors" href="#brokerconfigs_group.consumer.assignors">group.consumer.assignors</a></h4>
-<p>The server side assignors as a list of either names for builtin assignors or full class names for customer assignors. The first one in the list is considered as the default assignor to be used in the case where the consumer does not specify an assignor. The supported builtin assignors are: uniform, range.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>uniform,range</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.heartbeat.interval.ms"></a><a id="brokerconfigs_group.consumer.heartbeat.interval.ms" href="#brokerconfigs_group.consumer.heartbeat.interval.ms">group.consumer.heartbeat.interval.ms</a></h4>
-<p>The heartbeat interval given to the members of a consumer group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.max.assignment.interval.ms"></a><a id="brokerconfigs_group.consumer.max.assignment.interval.ms" href="#brokerconfigs_group.consumer.max.assignment.interval.ms">group.consumer.max.assignment.interval.ms</a></h4>
-<p>The maximum interval between assignment updates for a consumer group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>15000 (15 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.max.heartbeat.interval.ms"></a><a id="brokerconfigs_group.consumer.max.heartbeat.interval.ms" href="#brokerconfigs_group.consumer.max.heartbeat.interval.ms">group.consumer.max.heartbeat.interval.ms</a></h4>
-<p>The maximum heartbeat interval for registered consumers.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>15000 (15 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.max.session.timeout.ms"></a><a id="brokerconfigs_group.consumer.max.session.timeout.ms" href="#brokerconfigs_group.consumer.max.session.timeout.ms">group.consumer.max.session.timeout.ms</a></h4>
-<p>The maximum allowed session timeout for registered consumers.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.max.size"></a><a id="brokerconfigs_group.consumer.max.size" href="#brokerconfigs_group.consumer.max.size">group.consumer.max.size</a></h4>
-<p>The maximum number of consumers that a single consumer group can accommodate. This value will only impact groups under the CONSUMER group protocol. To configure the max group size when using the CLASSIC group protocol use group.max.size instead.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2147483647</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.migration.policy"></a><a id="brokerconfigs_group.consumer.migration.policy" href="#brokerconfigs_group.consumer.migration.policy">group.consumer.migration.policy</a></h4>
-<p>The config that enables converting the non-empty classic group using the consumer embedded protocol to the non-empty consumer group using the consumer group protocol and vice versa; conversions of empty groups in both directions are always enabled regardless of this policy. bidirectional: both upgrade from classic group to consumer group and downgrade from consumer group to classic group are enabled, upgrade: only upgrade from classic group to consumer group is enabled, downgrade: onl [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>bidirectional</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [DISABLED, DOWNGRADE, UPGRADE, BIDIRECTIONAL]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.min.assignment.interval.ms"></a><a id="brokerconfigs_group.consumer.min.assignment.interval.ms" href="#brokerconfigs_group.consumer.min.assignment.interval.ms">group.consumer.min.assignment.interval.ms</a></h4>
-<p>The minimum interval between assignment updates for a consumer group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.min.heartbeat.interval.ms"></a><a id="brokerconfigs_group.consumer.min.heartbeat.interval.ms" href="#brokerconfigs_group.consumer.min.heartbeat.interval.ms">group.consumer.min.heartbeat.interval.ms</a></h4>
-<p>The minimum heartbeat interval for registered consumers.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.min.session.timeout.ms"></a><a id="brokerconfigs_group.consumer.min.session.timeout.ms" href="#brokerconfigs_group.consumer.min.session.timeout.ms">group.consumer.min.session.timeout.ms</a></h4>
-<p>The minimum allowed session timeout for registered consumers.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.consumer.session.timeout.ms"></a><a id="brokerconfigs_group.consumer.session.timeout.ms" href="#brokerconfigs_group.consumer.session.timeout.ms">group.consumer.session.timeout.ms</a></h4>
-<p>The timeout to detect client failures when using the consumer group protocol.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.coordinator.append.linger.ms"></a><a id="brokerconfigs_group.coordinator.append.linger.ms" href="#brokerconfigs_group.coordinator.append.linger.ms">group.coordinator.append.linger.ms</a></h4>
-<p>The duration in milliseconds that the coordinator will wait for writes to accumulate before flushing them to disk. Increasing this value improves write efficiency and batch size, but also increases the response latency for requests, as the coordinator must wait for batches to be flushed to disk before completing request processing. Transactional writes are not accumulated. Set to -1 for an adaptive linger time that minimizes latency based on the workload.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>-1</td></tr>
-<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.coordinator.cached.buffer.max.bytes"></a><a id="brokerconfigs_group.coordinator.cached.buffer.max.bytes" href="#brokerconfigs_group.coordinator.cached.buffer.max.bytes">group.coordinator.cached.buffer.max.bytes</a></h4>
-<p>The maximum buffer size that the GroupCoordinator will retain for reuse. Note: Setting this larger than the maximum message size is not recommended. In this case, every write buffer will be eligible for recycling, which renders this configuration ineffective as a size limit.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1048588</td></tr>
-<tr><th>Valid Values:</th><td>[524288,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.coordinator.rebalance.protocols"></a><a id="brokerconfigs_group.coordinator.rebalance.protocols" href="#brokerconfigs_group.coordinator.rebalance.protocols">group.coordinator.rebalance.protocols</a></h4>
-<p>This configuration is deprecated and will be removed in Kafka 5.0. The list of enabled rebalance protocols. In Kafka 5.0, all protocols will always be enabled and cannot be disabled via this configuration. Use feature versions (group.version, streams.version, share.version) managed by kafka-features.sh instead.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>classic,consumer,streams</td></tr>
-<tr><th>Valid Values:</th><td>[consumer, classic, share, streams]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.initial.rebalance.delay.ms"></a><a id="brokerconfigs_group.initial.rebalance.delay.ms" href="#brokerconfigs_group.initial.rebalance.delay.ms">group.initial.rebalance.delay.ms</a></h4>
-<p>The amount of time the group coordinator will wait for more consumers to join a new group before performing the first rebalance. A longer delay means potentially fewer rebalances, but increases the time until processing begins.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>3000 (3 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.max.session.timeout.ms"></a><a id="brokerconfigs_group.max.session.timeout.ms" href="#brokerconfigs_group.max.session.timeout.ms">group.max.session.timeout.ms</a></h4>
-<p>The maximum allowed session timeout for registered consumers. Longer timeouts give consumers more time to process messages in between heartbeats at the cost of a longer time to detect failures.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1800000 (30 minutes)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.max.size"></a><a id="brokerconfigs_group.max.size" href="#brokerconfigs_group.max.size">group.max.size</a></h4>
-<p>The maximum number of consumers that a single consumer group can accommodate.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2147483647</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.min.session.timeout.ms"></a><a id="brokerconfigs_group.min.session.timeout.ms" href="#brokerconfigs_group.min.session.timeout.ms">group.min.session.timeout.ms</a></h4>
-<p>The minimum allowed session timeout for registered consumers. Shorter timeouts result in quicker failure detection at the cost of more frequent consumer heartbeating, which can overwhelm broker resources.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>6000 (6 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.assignment.interval.ms"></a><a id="brokerconfigs_group.share.assignment.interval.ms" href="#brokerconfigs_group.share.assignment.interval.ms">group.share.assignment.interval.ms</a></h4>
-<p>The interval between assignment updates for a share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.assignors"></a><a id="brokerconfigs_group.share.assignors" href="#brokerconfigs_group.share.assignors">group.share.assignors</a></h4>
-<p>The server-side assignors as a list of either names for built-in assignors or full class names for custom assignors. The list must contain only a single entry which is used by all groups. The supported built-in assignors are: simple.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>simple</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.delivery.count.limit"></a><a id="brokerconfigs_group.share.delivery.count.limit" href="#brokerconfigs_group.share.delivery.count.limit">group.share.delivery.count.limit</a></h4>
-<p>The maximum number of delivery attempts for a record delivered to a share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5</td></tr>
-<tr><th>Valid Values:</th><td>[2,...,10]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.heartbeat.interval.ms"></a><a id="brokerconfigs_group.share.heartbeat.interval.ms" href="#brokerconfigs_group.share.heartbeat.interval.ms">group.share.heartbeat.interval.ms</a></h4>
-<p>The heartbeat interval given to the members of a share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.max.assignment.interval.ms"></a><a id="brokerconfigs_group.share.max.assignment.interval.ms" href="#brokerconfigs_group.share.max.assignment.interval.ms">group.share.max.assignment.interval.ms</a></h4>
-<p>The maximum interval between assignment updates for a share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>15000 (15 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.max.delivery.count.limit"></a><a id="brokerconfigs_group.share.max.delivery.count.limit" href="#brokerconfigs_group.share.max.delivery.count.limit">group.share.max.delivery.count.limit</a></h4>
-<p>The maximum value of a group configuration for the maximum number of delivery attempts for a record delivered to a share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10</td></tr>
-<tr><th>Valid Values:</th><td>[5,...,25]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.max.heartbeat.interval.ms"></a><a id="brokerconfigs_group.share.max.heartbeat.interval.ms" href="#brokerconfigs_group.share.max.heartbeat.interval.ms">group.share.max.heartbeat.interval.ms</a></h4>
-<p>The maximum heartbeat interval for share group members.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>15000 (15 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.max.partition.max.record.locks"></a><a id="brokerconfigs_group.share.max.partition.max.record.locks" href="#brokerconfigs_group.share.max.partition.max.record.locks">group.share.max.partition.max.record.locks</a></h4>
-<p>The maximum value of a group configuration for the record lock limit per share-partition.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>4000</td></tr>
-<tr><th>Valid Values:</th><td>[2000,...,10000]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.max.record.lock.duration.ms"></a><a id="brokerconfigs_group.share.max.record.lock.duration.ms" href="#brokerconfigs_group.share.max.record.lock.duration.ms">group.share.max.record.lock.duration.ms</a></h4>
-<p>The maximum value of a group configuration for record acquisition lock duration in milliseconds.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td>[30000,...,3600000]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.max.session.timeout.ms"></a><a id="brokerconfigs_group.share.max.session.timeout.ms" href="#brokerconfigs_group.share.max.session.timeout.ms">group.share.max.session.timeout.ms</a></h4>
-<p>The maximum allowed session timeout for share group members.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.max.share.sessions"></a><a id="brokerconfigs_group.share.max.share.sessions" href="#brokerconfigs_group.share.max.share.sessions">group.share.max.share.sessions</a></h4>
-<p>The maximum number of share sessions per broker.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2000</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.max.size"></a><a id="brokerconfigs_group.share.max.size" href="#brokerconfigs_group.share.max.size">group.share.max.size</a></h4>
-<p>The maximum number of members that a single share group can accommodate.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>200</td></tr>
-<tr><th>Valid Values:</th><td>[1,...,1000]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.min.assignment.interval.ms"></a><a id="brokerconfigs_group.share.min.assignment.interval.ms" href="#brokerconfigs_group.share.min.assignment.interval.ms">group.share.min.assignment.interval.ms</a></h4>
-<p>The minimum interval between assignment updates for a share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.min.delivery.count.limit"></a><a id="brokerconfigs_group.share.min.delivery.count.limit" href="#brokerconfigs_group.share.min.delivery.count.limit">group.share.min.delivery.count.limit</a></h4>
-<p>The minimum value of a group configuration for the maximum number of delivery attempts for a record delivered to a share group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[2,...,5]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.min.heartbeat.interval.ms"></a><a id="brokerconfigs_group.share.min.heartbeat.interval.ms" href="#brokerconfigs_group.share.min.heartbeat.interval.ms">group.share.min.heartbeat.interval.ms</a></h4>
-<p>The minimum heartbeat interval for share group members.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.min.partition.max.record.locks"></a><a id="brokerconfigs_group.share.min.partition.max.record.locks" href="#brokerconfigs_group.share.min.partition.max.record.locks">group.share.min.partition.max.record.locks</a></h4>
-<p>The minimum value of a group configuration for the record lock limit per share-partition.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td>[100,...,2000]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.min.record.lock.duration.ms"></a><a id="brokerconfigs_group.share.min.record.lock.duration.ms" href="#brokerconfigs_group.share.min.record.lock.duration.ms">group.share.min.record.lock.duration.ms</a></h4>
-<p>The minimum value of a group configuration for record acquisition lock duration in milliseconds.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>15000 (15 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1000,...,30000]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.min.session.timeout.ms"></a><a id="brokerconfigs_group.share.min.session.timeout.ms" href="#brokerconfigs_group.share.min.session.timeout.ms">group.share.min.session.timeout.ms</a></h4>
-<p>The minimum allowed session timeout for share group members.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.partition.max.record.locks"></a><a id="brokerconfigs_group.share.partition.max.record.locks" href="#brokerconfigs_group.share.partition.max.record.locks">group.share.partition.max.record.locks</a></h4>
-<p>Share-group record lock limit per share-partition.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2000</td></tr>
-<tr><th>Valid Values:</th><td>[100,...,10000]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.record.lock.duration.ms"></a><a id="brokerconfigs_group.share.record.lock.duration.ms" href="#brokerconfigs_group.share.record.lock.duration.ms">group.share.record.lock.duration.ms</a></h4>
-<p>The record acquisition lock duration in milliseconds for share groups.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1000,...,3600000]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.share.session.timeout.ms"></a><a id="brokerconfigs_group.share.session.timeout.ms" href="#brokerconfigs_group.share.session.timeout.ms">group.share.session.timeout.ms</a></h4>
-<p>The timeout to detect client failures when using the share group protocol.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.assignment.interval.ms"></a><a id="brokerconfigs_group.streams.assignment.interval.ms" href="#brokerconfigs_group.streams.assignment.interval.ms">group.streams.assignment.interval.ms</a></h4>
-<p>The interval between assignment updates for a streams group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.heartbeat.interval.ms"></a><a id="brokerconfigs_group.streams.heartbeat.interval.ms" href="#brokerconfigs_group.streams.heartbeat.interval.ms">group.streams.heartbeat.interval.ms</a></h4>
-<p>The heartbeat interval given to the members.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.initial.rebalance.delay.ms"></a><a id="brokerconfigs_group.streams.initial.rebalance.delay.ms" href="#brokerconfigs_group.streams.initial.rebalance.delay.ms">group.streams.initial.rebalance.delay.ms</a></h4>
-<p>The amount of time the group coordinator will wait for more streams clients to join a new group before performing the first rebalance. A longer delay means potentially fewer rebalances.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>3000 (3 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.max.assignment.interval.ms"></a><a id="brokerconfigs_group.streams.max.assignment.interval.ms" href="#brokerconfigs_group.streams.max.assignment.interval.ms">group.streams.max.assignment.interval.ms</a></h4>
-<p>The maximum interval between assignment updates for a streams group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>15000 (15 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.max.heartbeat.interval.ms"></a><a id="brokerconfigs_group.streams.max.heartbeat.interval.ms" href="#brokerconfigs_group.streams.max.heartbeat.interval.ms">group.streams.max.heartbeat.interval.ms</a></h4>
-<p>The maximum allowed value for the group-level configuration of streams.heartbeat.interval.ms</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>15000 (15 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.max.session.timeout.ms"></a><a id="brokerconfigs_group.streams.max.session.timeout.ms" href="#brokerconfigs_group.streams.max.session.timeout.ms">group.streams.max.session.timeout.ms</a></h4>
-<p>The maximum allowed value for the group-level configuration of streams.session.timeout.ms</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.max.size"></a><a id="brokerconfigs_group.streams.max.size" href="#brokerconfigs_group.streams.max.size">group.streams.max.size</a></h4>
-<p>The maximum number of streams clients that a single streams group can accommodate.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2147483647</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.max.standby.replicas"></a><a id="brokerconfigs_group.streams.max.standby.replicas" href="#brokerconfigs_group.streams.max.standby.replicas">group.streams.max.standby.replicas</a></h4>
-<p>The maximum allowed value for the group-level configuration of streams.num.standby.replicas</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.min.assignment.interval.ms"></a><a id="brokerconfigs_group.streams.min.assignment.interval.ms" href="#brokerconfigs_group.streams.min.assignment.interval.ms">group.streams.min.assignment.interval.ms</a></h4>
-<p>The minimum interval between assignment updates for a streams group.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.min.heartbeat.interval.ms"></a><a id="brokerconfigs_group.streams.min.heartbeat.interval.ms" href="#brokerconfigs_group.streams.min.heartbeat.interval.ms">group.streams.min.heartbeat.interval.ms</a></h4>
-<p>The minimum allowed value for the group-level configuration of streams.heartbeat.interval.ms</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>5000 (5 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.min.session.timeout.ms"></a><a id="brokerconfigs_group.streams.min.session.timeout.ms" href="#brokerconfigs_group.streams.min.session.timeout.ms">group.streams.min.session.timeout.ms</a></h4>
-<p>The minimum allowed value for the group-level configuration of streams.session.timeout.ms</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.num.standby.replicas"></a><a id="brokerconfigs_group.streams.num.standby.replicas" href="#brokerconfigs_group.streams.num.standby.replicas">group.streams.num.standby.replicas</a></h4>
-<p>The number of standby replicas for each task.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.streams.session.timeout.ms"></a><a id="brokerconfigs_group.streams.session.timeout.ms" href="#brokerconfigs_group.streams.session.timeout.ms">group.streams.session.timeout.ms</a></h4>
-<p>The timeout to detect client failures when using the streams group protocol.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>45000 (45 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="initial.broker.registration.timeout.ms"></a><a id="brokerconfigs_initial.broker.registration.timeout.ms" href="#brokerconfigs_initial.broker.registration.timeout.ms">initial.broker.registration.timeout.ms</a></h4>
-<p>When initially registering with the controller quorum, the number of milliseconds to wait before declaring failure and exiting the broker process.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="inter.broker.listener.name"></a><a id="brokerconfigs_inter.broker.listener.name" href="#brokerconfigs_inter.broker.listener.name">inter.broker.listener.name</a></h4>
-<p>Name of listener used for communication between brokers. If this is unset, the listener name is defined by security.inter.broker.protocol. It is an error to set this and security.inter.broker.protocol properties at the same time.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="leader.replication.throttled.rate"></a><a id="brokerconfigs_leader.replication.throttled.rate" href="#brokerconfigs_leader.replication.throttled.rate">leader.replication.throttled.rate</a></h4>
-<p>A long representing the upper bound (bytes/sec) on replication traffic for leaders enumerated in the property leader.replication.throttled.replicas (for each topic). This property can be only set dynamically. It is suggested that the limit be kept above 1MB/s for accurate behaviour.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>9223372036854775807</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.backoff.ms"></a><a id="brokerconfigs_log.cleaner.backoff.ms" href="#brokerconfigs_log.cleaner.backoff.ms">log.cleaner.backoff.ms</a></h4>
-<p>The amount of time to sleep when there are no logs to clean</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>15000 (15 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.dedupe.buffer.size"></a><a id="brokerconfigs_log.cleaner.dedupe.buffer.size" href="#brokerconfigs_log.cleaner.dedupe.buffer.size">log.cleaner.dedupe.buffer.size</a></h4>
-<p>The total memory used for log deduplication across all cleaner threads</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>134217728</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.delete.retention.ms"></a><a id="brokerconfigs_log.cleaner.delete.retention.ms" href="#brokerconfigs_log.cleaner.delete.retention.ms">log.cleaner.delete.retention.ms</a></h4>
-<p>The amount of time to retain tombstone message markers for log compacted topics. This setting also gives a bound on the time in which a consumer must complete a read if they begin from offset 0 to ensure that they get a valid snapshot of the final stage (otherwise tombstones messages may be collected before a consumer completes their scan).</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>86400000 (1 day)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.enable"></a><a id="brokerconfigs_log.cleaner.enable" href="#brokerconfigs_log.cleaner.enable">log.cleaner.enable</a></h4>
-<p>This configuration has been deprecated and will be removed in Kafka 5.0. Users should not set it to false to prepare for its future removal. Enable the log cleaner process to run on the server. Should be enabled if using any topics with a cleanup.policy=compact including the internal offsets topic. If disabled those topics will not be compacted and continually grow in size.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.io.buffer.load.factor"></a><a id="brokerconfigs_log.cleaner.io.buffer.load.factor" href="#brokerconfigs_log.cleaner.io.buffer.load.factor">log.cleaner.io.buffer.load.factor</a></h4>
-<p>Log cleaner dedupe buffer load factor. The percentage full the dedupe buffer can become. A higher value will allow more log to be cleaned at once but will lead to more hash collisions</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.9</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.io.buffer.size"></a><a id="brokerconfigs_log.cleaner.io.buffer.size" href="#brokerconfigs_log.cleaner.io.buffer.size">log.cleaner.io.buffer.size</a></h4>
-<p>The total memory used for log cleaner I/O buffers across all cleaner threads</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>524288</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.io.max.bytes.per.second"></a><a id="brokerconfigs_log.cleaner.io.max.bytes.per.second" href="#brokerconfigs_log.cleaner.io.max.bytes.per.second">log.cleaner.io.max.bytes.per.second</a></h4>
-<p>The log cleaner will be throttled so that the sum of its read and write i/o will be less than this value on average</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>1.7976931348623157E308</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.max.compaction.lag.ms"></a><a id="brokerconfigs_log.cleaner.max.compaction.lag.ms" href="#brokerconfigs_log.cleaner.max.compaction.lag.ms">log.cleaner.max.compaction.lag.ms</a></h4>
-<p>The maximum time a message will remain ineligible for compaction in the log. Only applicable for logs that are being compacted.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>9223372036854775807</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.min.cleanable.ratio"></a><a id="brokerconfigs_log.cleaner.min.cleanable.ratio" href="#brokerconfigs_log.cleaner.min.cleanable.ratio">log.cleaner.min.cleanable.ratio</a></h4>
-<p>The minimum ratio of dirty log to total log for a log to eligible for cleaning. If the log.cleaner.max.compaction.lag.ms or the log.cleaner.min.compaction.lag.ms configurations are also specified, then the log compactor considers the log eligible for compaction as soon as either: (i) the dirty ratio threshold has been met and the log has had dirty (uncompacted) records for at least the log.cleaner.min.compaction.lag.ms duration, or (ii) if the log has had dirty (uncompacted) records f [...]
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.5</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,1]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.min.compaction.lag.ms"></a><a id="brokerconfigs_log.cleaner.min.compaction.lag.ms" href="#brokerconfigs_log.cleaner.min.compaction.lag.ms">log.cleaner.min.compaction.lag.ms</a></h4>
-<p>The minimum time a message will remain uncompacted in the log. Only applicable for logs that are being compacted.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleaner.threads"></a><a id="brokerconfigs_log.cleaner.threads" href="#brokerconfigs_log.cleaner.threads">log.cleaner.threads</a></h4>
-<p>The number of background threads to use for log cleaning</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.cleanup.policy"></a><a id="brokerconfigs_log.cleanup.policy" href="#brokerconfigs_log.cleanup.policy">log.cleanup.policy</a></h4>
-<p>This config designates the retention policy to use on log segments. The "delete" policy (which is the default) will discard old segments when their retention time or size limit has been reached. The "compact" policy will enable <a href="#compaction">log compaction</a>, which retains the latest value for each key. It is also possible to specify both policies in a comma-separated list (e.g. "delete,compact"). In this case, old segments will be discarded per the retention time and size c [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>delete</td></tr>
-<tr><th>Valid Values:</th><td>[compact, delete]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.index.interval.bytes"></a><a id="brokerconfigs_log.index.interval.bytes" href="#brokerconfigs_log.index.interval.bytes">log.index.interval.bytes</a></h4>
-<p>The interval with which we add an entry to the offset index.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>4096 (4 kibibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.index.size.max.bytes"></a><a id="brokerconfigs_log.index.size.max.bytes" href="#brokerconfigs_log.index.size.max.bytes">log.index.size.max.bytes</a></h4>
-<p>The maximum size in bytes of the offset index</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10485760 (10 mebibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[4,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.local.retention.bytes"></a><a id="brokerconfigs_log.local.retention.bytes" href="#brokerconfigs_log.local.retention.bytes">log.local.retention.bytes</a></h4>
-<p>The maximum size of local log segments that can grow for a partition before it gets eligible for deletion. Default value is -2, it represents <code>log.retention.bytes</code> value to be used. The effective value should always be less than or equal to <code>log.retention.bytes</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>-2</td></tr>
-<tr><th>Valid Values:</th><td>[-2,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.local.retention.ms"></a><a id="brokerconfigs_log.local.retention.ms" href="#brokerconfigs_log.local.retention.ms">log.local.retention.ms</a></h4>
-<p>The number of milliseconds to keep the local log segments before it gets eligible for deletion. Default value is -2, it represents <code>log.retention.ms</code> value is to be used. The effective value should always be less than or equal to <code>log.retention.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>-2</td></tr>
-<tr><th>Valid Values:</th><td>[-2,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.message.timestamp.after.max.ms"></a><a id="brokerconfigs_log.message.timestamp.after.max.ms" href="#brokerconfigs_log.message.timestamp.after.max.ms">log.message.timestamp.after.max.ms</a></h4>
-<p>This configuration sets the allowable timestamp difference between the message timestamp and the broker's timestamp. The message timestamp can be later than or equal to the broker's timestamp, with the maximum allowable difference determined by the value set in this configuration. If log.message.timestamp.type=CreateTime, the message will be rejected if the difference in timestamps exceeds this specified threshold. This configuration is ignored if log.message.timestamp.type=LogAppendT [...]
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.message.timestamp.before.max.ms"></a><a id="brokerconfigs_log.message.timestamp.before.max.ms" href="#brokerconfigs_log.message.timestamp.before.max.ms">log.message.timestamp.before.max.ms</a></h4>
-<p>This configuration sets the allowable timestamp difference between the broker's timestamp and the message timestamp. The message timestamp can be earlier than or equal to the broker's timestamp, with the maximum allowable difference determined by the value set in this configuration. If log.message.timestamp.type=CreateTime, the message will be rejected if the difference in timestamps exceeds this specified threshold. This configuration is ignored if log.message.timestamp.type=LogAppen [...]
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>9223372036854775807</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.message.timestamp.type"></a><a id="brokerconfigs_log.message.timestamp.type" href="#brokerconfigs_log.message.timestamp.type">log.message.timestamp.type</a></h4>
-<p>Define whether the timestamp in the message is message create time or log append time. The value should be either <code>CreateTime</code> or <code>LogAppendTime</code>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>CreateTime</td></tr>
-<tr><th>Valid Values:</th><td>[CreateTime, LogAppendTime]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.preallocate"></a><a id="brokerconfigs_log.preallocate" href="#brokerconfigs_log.preallocate">log.preallocate</a></h4>
-<p>Should pre allocate file when create new segment? If you are using Kafka on Windows, you probably need to set it to true.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.retention.check.interval.ms"></a><a id="brokerconfigs_log.retention.check.interval.ms" href="#brokerconfigs_log.retention.check.interval.ms">log.retention.check.interval.ms</a></h4>
-<p>The frequency in milliseconds that the log cleaner checks whether any log is eligible for deletion</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>300000 (5 minutes)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="max.connection.creation.rate"></a><a id="brokerconfigs_max.connection.creation.rate" href="#brokerconfigs_max.connection.creation.rate">max.connection.creation.rate</a></h4>
-<p>The maximum connection creation rate we allow in the broker at any time. Listener-level limits may also be configured by prefixing the config name with the listener prefix, for example, <code>listener.name.internal.max.connection.creation.rate</code>.Broker-wide connection rate limit should be configured based on broker capacity while listener limits should be configured based on application requirements. New connections will be throttled if either the listener or the broker limit is [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2147483647</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="max.connections"></a><a id="brokerconfigs_max.connections" href="#brokerconfigs_max.connections">max.connections</a></h4>
-<p>The maximum number of connections we allow in the broker at any time. This limit is applied in addition to any per-ip limits configured using max.connections.per.ip. Listener-level limits may also be configured by prefixing the config name with the listener prefix, for example, <code>listener.name.internal.max.connections.per.ip</code>. Broker-wide limit should be configured based on broker capacity while listener limits should be configured based on application requirements. New conn [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2147483647</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="max.connections.per.ip"></a><a id="brokerconfigs_max.connections.per.ip" href="#brokerconfigs_max.connections.per.ip">max.connections.per.ip</a></h4>
-<p>The maximum number of connections we allow from each ip address. This can be set to 0 if there are overrides configured using max.connections.per.ip.overrides property. New connections from the ip address are dropped if the limit is reached.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2147483647</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="max.connections.per.ip.overrides"></a><a id="brokerconfigs_max.connections.per.ip.overrides" href="#brokerconfigs_max.connections.per.ip.overrides">max.connections.per.ip.overrides</a></h4>
-<p>A comma-separated list of per-ip or hostname overrides to the default maximum number of connections. An example value is "hostName:100,127.0.0.1:200"</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="max.incremental.fetch.session.cache.slots"></a><a id="brokerconfigs_max.incremental.fetch.session.cache.slots" href="#brokerconfigs_max.incremental.fetch.session.cache.slots">max.incremental.fetch.session.cache.slots</a></h4>
-<p>The maximum number of total incremental fetch sessions that we will maintain. FetchSessionCache is sharded into 8 shards and the limit is equally divided among all shards. Sessions are allocated to each shard in round-robin. Only entries within a shard are considered eligible for eviction.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="max.request.partition.size.limit"></a><a id="brokerconfigs_max.request.partition.size.limit" href="#brokerconfigs_max.request.partition.size.limit">max.request.partition.size.limit</a></h4>
-<p>The maximum number of partitions can be served in one request.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2000</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="num.partitions"></a><a id="brokerconfigs_num.partitions" href="#brokerconfigs_num.partitions">num.partitions</a></h4>
-<p>The default number of log partitions per topic. This configuration affects the following paths:<ul> <li>1. Auto topic creation</li> <li>2. Internal streams topic creation</li> <li>3. Topic creation via <code>AdminClient#createTopics</code> when the number of partition is set to -1</li></ul><p>For (1), the value from the broker configuration is used only when it is explicitly set. If it is not explicitly configured on the broker, the value from the controller configuration is used.< [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="principal.builder.class"></a><a id="brokerconfigs_principal.builder.class" href="#brokerconfigs_principal.builder.class">principal.builder.class</a></h4>
-<p>The fully qualified name of a class that implements the KafkaPrincipalBuilder interface, which is used to build the KafkaPrincipal object used during authorization. If no principal builder is defined, the default behavior depends on the security protocol in use. For SSL authentication, the principal will be derived using the rules defined by <code>ssl.principal.mapping.rules</code> applied on the distinguished name from the client certificate if one is provided; otherwise, if client [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.authenticator.DefaultKafkaPrincipalBuilder</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="producer.purgatory.purge.interval.requests"></a><a id="brokerconfigs_producer.purgatory.purge.interval.requests" href="#brokerconfigs_producer.purgatory.purge.interval.requests">producer.purgatory.purge.interval.requests</a></h4>
-<p>The purge interval (in number of requests) of the producer request purgatory</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="queued.max.request.bytes"></a><a id="brokerconfigs_queued.max.request.bytes" href="#brokerconfigs_queued.max.request.bytes">queued.max.request.bytes</a></h4>
-<p>The number of queued bytes allowed before no more requests are read</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>-1</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.fetch.max.wait.ms"></a><a id="brokerconfigs_remote.fetch.max.wait.ms" href="#brokerconfigs_remote.fetch.max.wait.ms">remote.fetch.max.wait.ms</a></h4>
-<p>The maximum amount of time the server will wait before answering the fetch request containing remote fetch partitions. It's important to be aware that the request will only be responded after all remote partitions have been successfully fetched, have failed, or this timeout is exceeded.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>500</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.list.offsets.request.timeout.ms"></a><a id="brokerconfigs_remote.list.offsets.request.timeout.ms" href="#brokerconfigs_remote.list.offsets.request.timeout.ms">remote.list.offsets.request.timeout.ms</a></h4>
-<p>The maximum amount of time the server will wait for the remote list offsets request to complete.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.copier.thread.pool.size"></a><a id="brokerconfigs_remote.log.manager.copier.thread.pool.size" href="#brokerconfigs_remote.log.manager.copier.thread.pool.size">remote.log.manager.copier.thread.pool.size</a></h4>
-<p>Size of the thread pool used in scheduling tasks to copy segments.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.copy.max.bytes.per.second"></a><a id="brokerconfigs_remote.log.manager.copy.max.bytes.per.second" href="#brokerconfigs_remote.log.manager.copy.max.bytes.per.second">remote.log.manager.copy.max.bytes.per.second</a></h4>
-<p>The maximum number of bytes that can be copied from local storage to remote storage per second. This is a global limit for all the partitions that are being copied from local storage to remote storage. The default value is Long.MAX_VALUE, which means there is no limit on the number of bytes that can be copied per second.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>9223372036854775807</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.copy.quota.window.num"></a><a id="brokerconfigs_remote.log.manager.copy.quota.window.num" href="#brokerconfigs_remote.log.manager.copy.quota.window.num">remote.log.manager.copy.quota.window.num</a></h4>
-<p>The number of samples to retain in memory for remote copy quota management. The default value is 11, which means there are 10 whole windows + 1 current window.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>11</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.copy.quota.window.size.seconds"></a><a id="brokerconfigs_remote.log.manager.copy.quota.window.size.seconds" href="#brokerconfigs_remote.log.manager.copy.quota.window.size.seconds">remote.log.manager.copy.quota.window.size.seconds</a></h4>
-<p>The time span of each sample for remote copy quota management. The default value is 1 second.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.expiration.thread.pool.size"></a><a id="brokerconfigs_remote.log.manager.expiration.thread.pool.size" href="#brokerconfigs_remote.log.manager.expiration.thread.pool.size">remote.log.manager.expiration.thread.pool.size</a></h4>
-<p>Size of the thread pool used in scheduling tasks to clean up the expired remote log segments.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.fetch.max.bytes.per.second"></a><a id="brokerconfigs_remote.log.manager.fetch.max.bytes.per.second" href="#brokerconfigs_remote.log.manager.fetch.max.bytes.per.second">remote.log.manager.fetch.max.bytes.per.second</a></h4>
-<p>The maximum number of bytes that can be fetched from remote storage to local storage per second. This is a global limit for all the partitions that are being fetched from remote storage to local storage. The default value is Long.MAX_VALUE, which means there is no limit on the number of bytes that can be fetched per second.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>9223372036854775807</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.fetch.quota.window.num"></a><a id="brokerconfigs_remote.log.manager.fetch.quota.window.num" href="#brokerconfigs_remote.log.manager.fetch.quota.window.num">remote.log.manager.fetch.quota.window.num</a></h4>
-<p>The number of samples to retain in memory for remote fetch quota management. The default value is 11, which means there are 10 whole windows + 1 current window.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>11</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.fetch.quota.window.size.seconds"></a><a id="brokerconfigs_remote.log.manager.fetch.quota.window.size.seconds" href="#brokerconfigs_remote.log.manager.fetch.quota.window.size.seconds">remote.log.manager.fetch.quota.window.size.seconds</a></h4>
-<p>The time span of each sample for remote fetch quota management. The default value is 1 second.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.follower.thread.pool.size"></a><a id="brokerconfigs_remote.log.manager.follower.thread.pool.size" href="#brokerconfigs_remote.log.manager.follower.thread.pool.size">remote.log.manager.follower.thread.pool.size</a></h4>
-<p>Size of the thread pool used in scheduling follower tasks to read the highest-uploaded remote-offset for follower partitions.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.thread.pool.size"></a><a id="brokerconfigs_remote.log.manager.thread.pool.size" href="#brokerconfigs_remote.log.manager.thread.pool.size">remote.log.manager.thread.pool.size</a></h4>
-<p>Size of the thread pool used in scheduling follower tasks to read the highest-uploaded remote-offset for follower partitions. This config is deprecated since 4.2, please use <code>remote.log.manager.follower.thread.pool.size</code> instead.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.metadata.manager.class.name"></a><a id="brokerconfigs_remote.log.metadata.manager.class.name" href="#brokerconfigs_remote.log.metadata.manager.class.name">remote.log.metadata.manager.class.name</a></h4>
-<p>Fully qualified class name of <code>RemoteLogMetadataManager</code> implementation.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.server.log.remote.metadata.storage.TopicBasedRemoteLogMetadataManager</td></tr>
-<tr><th>Valid Values:</th><td>non-empty string</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.metadata.manager.class.path"></a><a id="brokerconfigs_remote.log.metadata.manager.class.path" href="#brokerconfigs_remote.log.metadata.manager.class.path">remote.log.metadata.manager.class.path</a></h4>
-<p>Class path of the <code>RemoteLogMetadataManager</code> implementation. If specified, the RemoteLogMetadataManager implementation and its dependent libraries will be loaded by a dedicated classloader which searches this class path before the Kafka broker class path. The syntax of this parameter is same as the standard Java class path string.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.metadata.manager.impl.prefix"></a><a id="brokerconfigs_remote.log.metadata.manager.impl.prefix" href="#brokerconfigs_remote.log.metadata.manager.impl.prefix">remote.log.metadata.manager.impl.prefix</a></h4>
-<p>Prefix used for properties to be passed to RemoteLogMetadataManager implementation. For example this value can be <code>rlmm.config.</code>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>rlmm.config.</td></tr>
-<tr><th>Valid Values:</th><td>non-empty string</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.metadata.manager.listener.name"></a><a id="brokerconfigs_remote.log.metadata.manager.listener.name" href="#brokerconfigs_remote.log.metadata.manager.listener.name">remote.log.metadata.manager.listener.name</a></h4>
-<p>Listener name of the local broker to which it should get connected if needed by RemoteLogMetadataManager implementation.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>non-empty string</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.reader.max.pending.tasks"></a><a id="brokerconfigs_remote.log.reader.max.pending.tasks" href="#brokerconfigs_remote.log.reader.max.pending.tasks">remote.log.reader.max.pending.tasks</a></h4>
-<p>Maximum remote log reader thread pool task queue size. If the task queue is full, fetch requests are served with an error.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.reader.threads"></a><a id="brokerconfigs_remote.log.reader.threads" href="#brokerconfigs_remote.log.reader.threads">remote.log.reader.threads</a></h4>
-<p>Size of the thread pool that is allocated for handling remote log reads.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.storage.manager.class.name"></a><a id="brokerconfigs_remote.log.storage.manager.class.name" href="#brokerconfigs_remote.log.storage.manager.class.name">remote.log.storage.manager.class.name</a></h4>
-<p>Fully qualified class name of <code>RemoteStorageManager</code> implementation.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>non-empty string</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.storage.manager.class.path"></a><a id="brokerconfigs_remote.log.storage.manager.class.path" href="#brokerconfigs_remote.log.storage.manager.class.path">remote.log.storage.manager.class.path</a></h4>
-<p>Class path of the <code>RemoteStorageManager</code> implementation. If specified, the RemoteStorageManager implementation and its dependent libraries will be loaded by a dedicated classloader which searches this class path before the Kafka broker class path. The syntax of this parameter is same as the standard Java class path string.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.storage.manager.impl.prefix"></a><a id="brokerconfigs_remote.log.storage.manager.impl.prefix" href="#brokerconfigs_remote.log.storage.manager.impl.prefix">remote.log.storage.manager.impl.prefix</a></h4>
-<p>Prefix used for properties to be passed to RemoteStorageManager implementation. For example this value can be <code>rsm.config.</code>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>rsm.config.</td></tr>
-<tr><th>Valid Values:</th><td>non-empty string</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.storage.system.enable"></a><a id="brokerconfigs_remote.log.storage.system.enable" href="#brokerconfigs_remote.log.storage.system.enable">remote.log.storage.system.enable</a></h4>
-<p>Whether to enable tiered storage functionality in a broker or not. When it is true broker starts all the services required for the tiered storage functionality.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.alter.log.dirs.io.max.bytes.per.second"></a><a id="brokerconfigs_replica.alter.log.dirs.io.max.bytes.per.second" href="#brokerconfigs_replica.alter.log.dirs.io.max.bytes.per.second">replica.alter.log.dirs.io.max.bytes.per.second</a></h4>
-<p>A long representing the upper bound (bytes/sec) on disk IO used for moving replica between log directories on the same broker. This property can be only set dynamically. It is suggested that the limit be kept above 1MB/s for accurate behaviour.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>9223372036854775807</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.fetch.backoff.ms"></a><a id="brokerconfigs_replica.fetch.backoff.ms" href="#brokerconfigs_replica.fetch.backoff.ms">replica.fetch.backoff.ms</a></h4>
-<p>The amount of time to sleep when fetch partition error occurs.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.fetch.max.bytes"></a><a id="brokerconfigs_replica.fetch.max.bytes" href="#brokerconfigs_replica.fetch.max.bytes">replica.fetch.max.bytes</a></h4>
-<p>The number of bytes of messages to attempt to fetch for each partition. This is not an absolute maximum, if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that progress can be made. The maximum record batch size accepted by the broker is defined via <code>message.max.bytes</code> (broker config) or <code>max.message.bytes</code> (topic config).</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1048576 (1 mebibyte)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.fetch.response.max.bytes"></a><a id="brokerconfigs_replica.fetch.response.max.bytes" href="#brokerconfigs_replica.fetch.response.max.bytes">replica.fetch.response.max.bytes</a></h4>
-<p>Maximum bytes expected for the entire fetch response. Records are fetched in batches, and if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that progress can be made. As such, this is not an absolute maximum. The maximum record batch size accepted by the broker is defined via <code>message.max.bytes</code> (broker config) or <code>max.message.bytes</code> (topic config).</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10485760 (10 mebibytes)</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replica.selector.class"></a><a id="brokerconfigs_replica.selector.class" href="#brokerconfigs_replica.selector.class">replica.selector.class</a></h4>
-<p>The fully qualified class name that implements ReplicaSelector. This is used by the broker to find the preferred read replica. By default, we use an implementation that returns the leader.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.client.callback.handler.class"></a><a id="brokerconfigs_sasl.client.callback.handler.class" href="#brokerconfigs_sasl.client.callback.handler.class">sasl.client.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.enabled.mechanisms"></a><a id="brokerconfigs_sasl.enabled.mechanisms" href="#brokerconfigs_sasl.enabled.mechanisms">sasl.enabled.mechanisms</a></h4>
-<p>The list of SASL mechanisms enabled in the Kafka server. The list may contain any mechanism for which a security provider is available. Only GSSAPI is enabled by default.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>GSSAPI</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.jaas.config"></a><a id="brokerconfigs_sasl.jaas.config" href="#brokerconfigs_sasl.jaas.config">sasl.jaas.config</a></h4>
-<p>JAAS login context parameters for SASL connections in the format used by JAAS configuration files. JAAS configuration file format is described <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html">here</a>. The format for the value is: <code>loginModuleClass controlFlag (optionName=optionValue)*;</code>. For brokers, the config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.kinit.cmd"></a><a id="brokerconfigs_sasl.kerberos.kinit.cmd" href="#brokerconfigs_sasl.kerberos.kinit.cmd">sasl.kerberos.kinit.cmd</a></h4>
-<p>Kerberos kinit command path.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>/usr/bin/kinit</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.min.time.before.relogin"></a><a id="brokerconfigs_sasl.kerberos.min.time.before.relogin" href="#brokerconfigs_sasl.kerberos.min.time.before.relogin">sasl.kerberos.min.time.before.relogin</a></h4>
-<p>Login thread sleep time between refresh attempts.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60000</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.principal.to.local.rules"></a><a id="brokerconfigs_sasl.kerberos.principal.to.local.rules" href="#brokerconfigs_sasl.kerberos.principal.to.local.rules">sasl.kerberos.principal.to.local.rules</a></h4>
-<p>A list of rules for mapping from principal names to short names (typically operating system usernames). The rules are evaluated in order and the first rule that matches a principal name is used to map it to a short name. Any later rules in the list are ignored. By default, principal names of the form <code>{username}/{hostname}@{REALM}</code> are mapped to <code>{username}</code>. For more details on the format please see <a href="#security_authz"> security authorization and acls</a>. [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>DEFAULT</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.service.name"></a><a id="brokerconfigs_sasl.kerberos.service.name" href="#brokerconfigs_sasl.kerberos.service.name">sasl.kerberos.service.name</a></h4>
-<p>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.ticket.renew.jitter"></a><a id="brokerconfigs_sasl.kerberos.ticket.renew.jitter" href="#brokerconfigs_sasl.kerberos.ticket.renew.jitter">sasl.kerberos.ticket.renew.jitter</a></h4>
-<p>Percentage of random jitter added to the renewal time.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.05</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.ticket.renew.window.factor"></a><a id="brokerconfigs_sasl.kerberos.ticket.renew.window.factor" href="#brokerconfigs_sasl.kerberos.ticket.renew.window.factor">sasl.kerberos.ticket.renew.window.factor</a></h4>
-<p>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.8</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.callback.handler.class"></a><a id="brokerconfigs_sasl.login.callback.handler.class" href="#brokerconfigs_sasl.login.callback.handler.class">sasl.login.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL login callback handler class that implements the AuthenticateCallbackHandler interface. For brokers, login callback handler config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.callback.handler.class=com.example.CustomScramLoginCallbackHandler</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.class"></a><a id="brokerconfigs_sasl.login.class" href="#brokerconfigs_sasl.login.class">sasl.login.class</a></h4>
-<p>The fully qualified name of a class that implements the Login interface. For brokers, login config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.class=com.example.CustomScramLogin</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.buffer.seconds"></a><a id="brokerconfigs_sasl.login.refresh.buffer.seconds" href="#brokerconfigs_sasl.login.refresh.buffer.seconds">sasl.login.refresh.buffer.seconds</a></h4>
-<p>The amount of buffer time before credential expiration to maintain when refreshing a credential, in seconds. If a refresh would otherwise occur closer to expiration than the number of buffer seconds then the refresh will be moved up to maintain as much of the buffer time as possible. Legal values are between 0 and 3600 (1 hour); a default value of 300 (5 minutes) is used if no value is specified. This value and sasl.login.refresh.min.period.seconds are both ignored if their sum excee [...]
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.min.period.seconds"></a><a id="brokerconfigs_sasl.login.refresh.min.period.seconds" href="#brokerconfigs_sasl.login.refresh.min.period.seconds">sasl.login.refresh.min.period.seconds</a></h4>
-<p>The desired minimum time for the login refresh thread to wait before refreshing a credential, in seconds. Legal values are between 0 and 900 (15 minutes); a default value of 60 (1 minute) is used if no value is specified. This value and sasl.login.refresh.buffer.seconds are both ignored if their sum exceeds the remaining lifetime of a credential. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.window.factor"></a><a id="brokerconfigs_sasl.login.refresh.window.factor" href="#brokerconfigs_sasl.login.refresh.window.factor">sasl.login.refresh.window.factor</a></h4>
-<p>Login refresh thread will sleep until the specified window factor relative to the credential's lifetime has been reached, at which time it will try to refresh the credential. Legal values are between 0.5 (50%) and 1.0 (100%) inclusive; a default value of 0.8 (80%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.8</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.window.jitter"></a><a id="brokerconfigs_sasl.login.refresh.window.jitter" href="#brokerconfigs_sasl.login.refresh.window.jitter">sasl.login.refresh.window.jitter</a></h4>
-<p>The maximum amount of random jitter relative to the credential's lifetime that is added to the login refresh thread's sleep time. Legal values are between 0 and 0.25 (25%) inclusive; a default value of 0.05 (5%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.05</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.mechanism.inter.broker.protocol"></a><a id="brokerconfigs_sasl.mechanism.inter.broker.protocol" href="#brokerconfigs_sasl.mechanism.inter.broker.protocol">sasl.mechanism.inter.broker.protocol</a></h4>
-<p>SASL mechanism used for inter-broker communication. Default is GSSAPI.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>GSSAPI</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.algorithm"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.algorithm" href="#brokerconfigs_sasl.oauthbearer.assertion.algorithm">sasl.oauthbearer.assertion.algorithm</a></h4>
-<p><p>The algorithm the Apache Kafka client should use to sign the assertion sent to the identity provider. It is also used as the value of the OAuth <code>alg</code> (Algorithm) header in the JWT assertion.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>RS256</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [ES256, RS256]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.aud"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.claim.aud" href="#brokerconfigs_sasl.oauthbearer.assertion.claim.aud">sasl.oauthbearer.assertion.claim.aud</a></h4>
-<p><p>The JWT <code>aud</code> (Audience) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.iss"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.claim.iss" href="#brokerconfigs_sasl.oauthbearer.assertion.claim.iss">sasl.oauthbearer.assertion.claim.iss</a></h4>
-<p><p>The value to be used as the <code>iss</code> (Issuer) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.jti.include"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.claim.jti.include" href="#brokerconfigs_sasl.oauthbearer.assertion.claim.jti.include">sasl.oauthbearer.assertion.claim.jti.include</a></h4>
-<p><p>Flag that determines if the JWT assertion should generate a unique ID for the JWT and include it in the <code>jti</code> (JWT ID) claim.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.sub"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.claim.sub" href="#brokerconfigs_sasl.oauthbearer.assertion.claim.sub">sasl.oauthbearer.assertion.claim.sub</a></h4>
-<p><p>The value to be used as the <code>sub</code> (Subject) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.file"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.file" href="#brokerconfigs_sasl.oauthbearer.assertion.file">sasl.oauthbearer.assertion.file</a></h4>
-<p><p>File that contains a <em>pre-generated</em> JWT assertion.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect whenthe file changes to allow for the file to be reloaded on modifications. This allows for "live" assertion rotation without restarting the Kafka client.</p><p>The file contains the assertion in the serialized, three part JWT format:</p><ol><li>The <em>hea [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.private.key.file"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.private.key.file" href="#brokerconfigs_sasl.oauthbearer.assertion.private.key.file">sasl.oauthbearer.assertion.private.key.file</a></h4>
-<p><p>File that contains a private key in the standard PEM format which is used to sign the JWT assertion sent to the identity provider.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect when the file changes to allow for the file to be reloaded on modifications. This allows for "live" private key rotation without restarting the Kafka client.</p><p><em>Note</em>: If a v [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.private.key.passphrase"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.private.key.passphrase" href="#brokerconfigs_sasl.oauthbearer.assertion.private.key.passphrase">sasl.oauthbearer.assertion.private.key.passphrase</a></h4>
-<p><p>The optional passphrase to decrypt the private key file specified by <code>sasl.oauthbearer.assertion.private.key.file</code>.</p><p><em>Note</em>: If the file referred to by <code>sasl.oauthbearer.assertion.private.key.file</code> is modified on the file system at runtime and it was created with a <em>different</em> passphrase than it was previously, the client will not be able to access the private key file because the passphrase is now out of date. For that reason, when using pr [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.template.file"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.template.file" href="#brokerconfigs_sasl.oauthbearer.assertion.template.file">sasl.oauthbearer.assertion.template.file</a></h4>
-<p><p>This optional configuration specifies the file containing the JWT headers and/or payload claims to be used when creating the JWT assertion.</p><p>Not all identity providers require the same set of claims; some may require a given claim while others may prohibit it. In order to provide the most flexibility, this configuration allows the user to provide the static header values and claims that are to be included in the JWT.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.a [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.client.credentials.client.id"></a><a id="brokerconfigs_sasl.oauthbearer.client.credentials.client.id" href="#brokerconfigs_sasl.oauthbearer.client.credentials.client.id">sasl.oauthbearer.client.credentials.client.id</a></h4>
-<p><p>The ID (defined in/by the OAuth identity provider) to identify the client requesting the token.</p><p>The client ID was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientId</code>. For backward compatibility, the <code>clientId</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.client.credentials.client.id</code> from conf [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.client.credentials.client.secret"></a><a id="brokerconfigs_sasl.oauthbearer.client.credentials.client.secret" href="#brokerconfigs_sasl.oauthbearer.client.credentials.client.secret">sasl.oauthbearer.client.credentials.client.secret</a></h4>
-<p><p>The secret (defined by either the user or preassigned, depending on the identity provider) of the client requesting the token.</p><p>The client secret was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientSecret</code>. For backward compatibility, the <code>clientSecret</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.cl [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.url"></a><a id="brokerconfigs_sasl.oauthbearer.jwks.endpoint.url" href="#brokerconfigs_sasl.oauthbearer.jwks.endpoint.url">sasl.oauthbearer.jwks.endpoint.url</a></h4>
-<p>The OAuth/OIDC provider URL from which the provider's <a href="https://datatracker.ietf.org/doc/html/rfc7517#section-5">JWKS (JSON Web Key Set)</a> can be retrieved. The URL can be HTTP(S)-based or file-based. If the URL is HTTP(S)-based, the JWKS data will be retrieved from the OAuth/OIDC provider via the configured URL on broker startup. All then-current keys will be cached on the broker for incoming requests. If an authentication request is received for a JWT that includes a "kid" [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwt.retriever.class"></a><a id="brokerconfigs_sasl.oauthbearer.jwt.retriever.class" href="#brokerconfigs_sasl.oauthbearer.jwt.retriever.class">sasl.oauthbearer.jwt.retriever.class</a></h4>
-<p><p>The fully-qualified class name of a <code>JwtRetriever</code> implementation used to request tokens from the identity provider.</p><p>The default configuration value represents a class that maintains backward compatibility with previous versions of Apache Kafka. The default implementation uses the configuration to determine which concrete implementation to create.<p>Other implementations that are provided include:</p><ul><li><code>org.apache.kafka.common.security.oauthbearer.Client [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtRetriever</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwt.validator.class"></a><a id="brokerconfigs_sasl.oauthbearer.jwt.validator.class" href="#brokerconfigs_sasl.oauthbearer.jwt.validator.class">sasl.oauthbearer.jwt.validator.class</a></h4>
-<p><p>The fully-qualified class name of a <code>JwtValidator</code> implementation used to validate the JWT from the identity provider.</p><p>The default validator (<code>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</code>) maintains backward compatibility with previous versions of Apache Kafka. The default validator uses configuration to determine which concrete implementation to create.<p>The built-in <code>JwtValidator</code> implementations are:</p><ul><li><code>o [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.scope"></a><a id="brokerconfigs_sasl.oauthbearer.scope" href="#brokerconfigs_sasl.oauthbearer.scope">sasl.oauthbearer.scope</a></h4>
-<p><p>This is the level of access a client application is granted to a resource or API which is included in the token request. If provided, it should match one or more scopes configured in the identity provider.</p><p>The scope was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>scope</code>. For backward compatibility, the <code>scope</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p> [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.token.endpoint.url"></a><a id="brokerconfigs_sasl.oauthbearer.token.endpoint.url" href="#brokerconfigs_sasl.oauthbearer.token.endpoint.url">sasl.oauthbearer.token.endpoint.url</a></h4>
-<p>The URL for the OAuth/OIDC identity provider. If the URL is HTTP(S)-based, it is the issuer's token endpoint URL to which requests will be made to login based on the configuration in <code>sasl.oauthbearer.jwt.retriever.class</code>. If the URL is file-based, it specifies a file containing an access token (in JWT serialized form) issued by the OAuth/OIDC identity provider to use for authorization.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.server.callback.handler.class"></a><a id="brokerconfigs_sasl.server.callback.handler.class" href="#brokerconfigs_sasl.server.callback.handler.class">sasl.server.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL server callback handler class that implements the AuthenticateCallbackHandler interface. Server callback handlers must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.plain.sasl.server.callback.handler.class=com.example.CustomPlainCallbackHandler.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.server.max.receive.size"></a><a id="brokerconfigs_sasl.server.max.receive.size" href="#brokerconfigs_sasl.server.max.receive.size">sasl.server.max.receive.size</a></h4>
-<p>The maximum receive size allowed before and during initial SASL authentication. Default receive size is 512KB. GSSAPI limits requests to 64K, but we allow upto 512KB by default for custom SASL mechanisms. In practice, PLAIN, SCRAM and OAUTH mechanisms can use much smaller limits.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>524288</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="security.inter.broker.protocol"></a><a id="brokerconfigs_security.inter.broker.protocol" href="#brokerconfigs_security.inter.broker.protocol">security.inter.broker.protocol</a></h4>
-<p>Security protocol used to communicate between brokers. It is an error to set this and inter.broker.listener.name properties at the same time.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>PLAINTEXT</td></tr>
-<tr><th>Valid Values:</th><td>[PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.append.linger.ms"></a><a id="brokerconfigs_share.coordinator.append.linger.ms" href="#brokerconfigs_share.coordinator.append.linger.ms">share.coordinator.append.linger.ms</a></h4>
-<p>The duration in milliseconds that the share coordinator will wait for writes to accumulate before flushing them to disk. Set to -1 for an adaptive linger time that minimizes latency based on the workload.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>-1</td></tr>
-<tr><th>Valid Values:</th><td>[-1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.cached.buffer.max.bytes"></a><a id="brokerconfigs_share.coordinator.cached.buffer.max.bytes" href="#brokerconfigs_share.coordinator.cached.buffer.max.bytes">share.coordinator.cached.buffer.max.bytes</a></h4>
-<p>The maximum buffer size that the ShareCoordinator will retain for reuse. Note: Setting this larger than the maximum message size is not recommended. In this case, every write buffer will be eligible for recycling, which renders this configuration ineffective as a size limit.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1048588</td></tr>
-<tr><th>Valid Values:</th><td>[524288,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.snapshot.update.records.per.snapshot"></a><a id="brokerconfigs_share.coordinator.snapshot.update.records.per.snapshot" href="#brokerconfigs_share.coordinator.snapshot.update.records.per.snapshot">share.coordinator.snapshot.update.records.per.snapshot</a></h4>
-<p>The number of update records the share coordinator writes between snapshot records.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>500</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,500]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.coordinator.threads"></a><a id="brokerconfigs_share.coordinator.threads" href="#brokerconfigs_share.coordinator.threads">share.coordinator.threads</a></h4>
-<p>The number of threads used by the share coordinator.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="share.fetch.purgatory.purge.interval.requests"></a><a id="brokerconfigs_share.fetch.purgatory.purge.interval.requests" href="#brokerconfigs_share.fetch.purgatory.purge.interval.requests">share.fetch.purgatory.purge.interval.requests</a></h4>
-<p>The purge interval (in number of requests) of the share fetch request purgatory</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1000</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.connection.setup.timeout.max.ms"></a><a id="brokerconfigs_socket.connection.setup.timeout.max.ms" href="#brokerconfigs_socket.connection.setup.timeout.max.ms">socket.connection.setup.timeout.max.ms</a></h4>
-<p>The maximum amount of time the client will wait for the socket connection to be established. The connection setup timeout will increase exponentially for each consecutive connection failure up to this maximum. To avoid connection storms, a randomization factor of 0.2 will be applied to the timeout resulting in a random range between 20% below and 20% above the computed value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.connection.setup.timeout.ms"></a><a id="brokerconfigs_socket.connection.setup.timeout.ms" href="#brokerconfigs_socket.connection.setup.timeout.ms">socket.connection.setup.timeout.ms</a></h4>
-<p>The amount of time the client will wait for the socket connection to be established. If the connection is not built before the timeout elapses, clients will close the socket channel. This value is the initial backoff value and will increase exponentially for each consecutive connection failure, up to the <code>socket.connection.setup.timeout.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="socket.listen.backlog.size"></a><a id="brokerconfigs_socket.listen.backlog.size" href="#brokerconfigs_socket.listen.backlog.size">socket.listen.backlog.size</a></h4>
-<p>The maximum number of pending connections on the socket. In Linux, you may also need to configure <code>somaxconn</code> and <code>tcp_max_syn_backlog</code> kernel parameters accordingly to make the configuration takes effect.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>50</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.cipher.suites"></a><a id="brokerconfigs_ssl.cipher.suites" href="#brokerconfigs_ssl.cipher.suites">ssl.cipher.suites</a></h4>
-<p>A list of cipher suites. This is a named combination of authentication, encryption, MAC and key exchange algorithm used to negotiate the security settings for a network connection using TLS or SSL network protocol. By default all the available cipher suites are supported.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.client.auth"></a><a id="brokerconfigs_ssl.client.auth" href="#brokerconfigs_ssl.client.auth">ssl.client.auth</a></h4>
-<p>Configures kafka broker to request client authentication. The following settings are common: <ul> <li><code>ssl.client.auth=required</code> If set to required client authentication is required. <li><code>ssl.client.auth=requested</code> This means client authentication is optional. unlike required, if this option is set client can choose not to provide authentication information about itself <li><code>ssl.client.auth=none</code> This means client authentication is not needed.</ul></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>none</td></tr>
-<tr><th>Valid Values:</th><td>[required, requested, none]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.enabled.protocols"></a><a id="brokerconfigs_ssl.enabled.protocols" href="#brokerconfigs_ssl.enabled.protocols">ssl.enabled.protocols</a></h4>
-<p>The list of protocols enabled for SSL connections. The default is 'TLSv1.2,TLSv1.3'. This means that clients and servers will prefer TLSv1.3 if both support it and fallback to TLSv1.2 otherwise (assuming both support at least TLSv1.2). This default should be fine for most use cases. If this configuration is set to an empty list, Kafka will use the protocols enabled by default in the underlying SSLEngine, which may include additional protocols depending on the JVM version. Also see the [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>TLSv1.2,TLSv1.3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.key.password"></a><a id="brokerconfigs_ssl.key.password" href="#brokerconfigs_ssl.key.password">ssl.key.password</a></h4>
-<p>The password of the private key in the key store file or the PEM key specified in 'ssl.keystore.key'.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keymanager.algorithm"></a><a id="brokerconfigs_ssl.keymanager.algorithm" href="#brokerconfigs_ssl.keymanager.algorithm">ssl.keymanager.algorithm</a></h4>
-<p>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>SunX509</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.certificate.chain"></a><a id="brokerconfigs_ssl.keystore.certificate.chain" href="#brokerconfigs_ssl.keystore.certificate.chain">ssl.keystore.certificate.chain</a></h4>
-<p>Certificate chain in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with a list of X.509 certificates</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.key"></a><a id="brokerconfigs_ssl.keystore.key" href="#brokerconfigs_ssl.keystore.key">ssl.keystore.key</a></h4>
-<p>Private key in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with PKCS#8 keys. If the key is encrypted, key password must be specified using 'ssl.key.password'</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.location"></a><a id="brokerconfigs_ssl.keystore.location" href="#brokerconfigs_ssl.keystore.location">ssl.keystore.location</a></h4>
-<p>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.password"></a><a id="brokerconfigs_ssl.keystore.password" href="#brokerconfigs_ssl.keystore.password">ssl.keystore.password</a></h4>
-<p>The store password for the key store file. This is optional for client and only needed if 'ssl.keystore.location' is configured. Key store password is not supported for PEM format.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.type"></a><a id="brokerconfigs_ssl.keystore.type" href="#brokerconfigs_ssl.keystore.type">ssl.keystore.type</a></h4>
-<p>The file format of the key store file. This is optional for client. The values currently supported by the default <code>ssl.engine.factory.class</code> are [JKS, PKCS12, PEM].</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>JKS</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.protocol"></a><a id="brokerconfigs_ssl.protocol" href="#brokerconfigs_ssl.protocol">ssl.protocol</a></h4>
-<p>The SSL protocol used to generate the SSLContext. The default is 'TLSv1.3', which should be fine for most use cases. A typical alternative to the default is 'TLSv1.2'. Allowed values for this config are dependent on the JVM. Clients using the defaults for this config and 'ssl.enabled.protocols' will downgrade to 'TLSv1.2' if the server does not support 'TLSv1.3'. If this config is set to 'TLSv1.2', however, clients will not use 'TLSv1.3' even if it is one of the values in <code>ssl.en [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>TLSv1.3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.provider"></a><a id="brokerconfigs_ssl.provider" href="#brokerconfigs_ssl.provider">ssl.provider</a></h4>
-<p>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.trustmanager.algorithm"></a><a id="brokerconfigs_ssl.trustmanager.algorithm" href="#brokerconfigs_ssl.trustmanager.algorithm">ssl.trustmanager.algorithm</a></h4>
-<p>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>PKIX</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.certificates"></a><a id="brokerconfigs_ssl.truststore.certificates" href="#brokerconfigs_ssl.truststore.certificates">ssl.truststore.certificates</a></h4>
-<p>Trusted certificates in the format specified by 'ssl.truststore.type'. Default SSL engine factory supports only PEM format with X.509 certificates.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.location"></a><a id="brokerconfigs_ssl.truststore.location" href="#brokerconfigs_ssl.truststore.location">ssl.truststore.location</a></h4>
-<p>The location of the trust store file.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.password"></a><a id="brokerconfigs_ssl.truststore.password" href="#brokerconfigs_ssl.truststore.password">ssl.truststore.password</a></h4>
-<p>The password for the trust store file. If a password is not set, trust store file configured will still be used, but integrity checking is disabled. Trust store password is not supported for PEM format.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.type"></a><a id="brokerconfigs_ssl.truststore.type" href="#brokerconfigs_ssl.truststore.type">ssl.truststore.type</a></h4>
-<p>The file format of the trust store file. The values currently supported by the default <code>ssl.engine.factory.class</code> are [JKS, PKCS12, PEM].</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>JKS</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="alter.config.policy.class.name"></a><a id="brokerconfigs_alter.config.policy.class.name" href="#brokerconfigs_alter.config.policy.class.name">alter.config.policy.class.name</a></h4>
-<p>The alter configs policy class that should be used for validation. The class should implement the <code>org.apache.kafka.server.policy.AlterConfigPolicy</code> interface. <p>Note: This policy runs on the controller instead of the broker.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="alter.log.dirs.replication.quota.window.num"></a><a id="brokerconfigs_alter.log.dirs.replication.quota.window.num" href="#brokerconfigs_alter.log.dirs.replication.quota.window.num">alter.log.dirs.replication.quota.window.num</a></h4>
-<p>The number of samples to retain in memory for alter log dirs replication quotas</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>11</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="alter.log.dirs.replication.quota.window.size.seconds"></a><a id="brokerconfigs_alter.log.dirs.replication.quota.window.size.seconds" href="#brokerconfigs_alter.log.dirs.replication.quota.window.size.seconds">alter.log.dirs.replication.quota.window.size.seconds</a></h4>
-<p>The time span of each sample for alter log dirs replication quotas</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="authorizer.class.name"></a><a id="brokerconfigs_authorizer.class.name" href="#brokerconfigs_authorizer.class.name">authorizer.class.name</a></h4>
-<p>The fully qualified name of a class that implements <code>org.apache.kafka.server.authorizer.Authorizer</code> interface, which is used by the broker for authorization.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td>non-null string</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="client.quota.callback.class"></a><a id="brokerconfigs_client.quota.callback.class" href="#brokerconfigs_client.quota.callback.class">client.quota.callback.class</a></h4>
-<p>The fully qualified name of a class that implements the ClientQuotaCallback interface, which is used to determine quota limits applied to client requests. By default, the <user> and <client-id> quotas that are stored and applied. For any given request, the most specific quota that matches the user principal of the session and the client-id of the request is applied.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="config.providers"></a><a id="brokerconfigs_config.providers" href="#brokerconfigs_config.providers">config.providers</a></h4>
-<p>Comma-separated alias names for classes implementing the <code>ConfigProvider</code> interface. This enables loading configuration data (such as passwords, API keys, and other credentials) from external sources. For example, see <a href="https://kafka.apache.org/documentation/#config_providers">Configuration Providers</a>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="connection.failed.authentication.delay.ms"></a><a id="brokerconfigs_connection.failed.authentication.delay.ms" href="#brokerconfigs_connection.failed.authentication.delay.ms">connection.failed.authentication.delay.ms</a></h4>
-<p>Connection close delay on failed authentication: this is the time (in milliseconds) by which connection close will be delayed on authentication failure. This must be configured to be less than connections.max.idle.ms to prevent connection timeout.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.auto.join.enable"></a><a id="brokerconfigs_controller.quorum.auto.join.enable" href="#brokerconfigs_controller.quorum.auto.join.enable">controller.quorum.auto.join.enable</a></h4>
-<p>Controls whether a KRaft controller should automatically join the cluster metadata partition for its cluster id.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.fetch.max.bytes"></a><a id="brokerconfigs_controller.quorum.fetch.max.bytes" href="#brokerconfigs_controller.quorum.fetch.max.bytes">controller.quorum.fetch.max.bytes</a></h4>
-<p>Maximum amount of data to retrieve for each Fetch request. Always returns at least one batch even if it is greater than controller.quorum.fetch.max.bytes.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1048576 (1 mebibyte)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.fetch.snapshot.max.bytes"></a><a id="brokerconfigs_controller.quorum.fetch.snapshot.max.bytes" href="#brokerconfigs_controller.quorum.fetch.snapshot.max.bytes">controller.quorum.fetch.snapshot.max.bytes</a></h4>
-<p>Maximum amount of data to retrieve for each FetchSnapshot request to the controller.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1048576 (1 mebibyte)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quorum.retry.backoff.ms"></a><a id="brokerconfigs_controller.quorum.retry.backoff.ms" href="#brokerconfigs_controller.quorum.retry.backoff.ms">controller.quorum.retry.backoff.ms</a></h4>
-<p>The amount of time to wait before attempting to retry a failed request to a given topic partition. This avoids repeatedly sending requests in a tight loop under some failure scenarios. This value is the initial backoff value and will increase exponentially for each failed request, up to the <code>retry.backoff.max.ms</code> value.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>20</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quota.window.num"></a><a id="brokerconfigs_controller.quota.window.num" href="#brokerconfigs_controller.quota.window.num">controller.quota.window.num</a></h4>
-<p>The number of samples to retain in memory for controller mutation quotas</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>11</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="controller.quota.window.size.seconds"></a><a id="brokerconfigs_controller.quota.window.size.seconds" href="#brokerconfigs_controller.quota.window.size.seconds">controller.quota.window.size.seconds</a></h4>
-<p>The time span of each sample for controller mutations quotas</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="create.topic.policy.class.name"></a><a id="brokerconfigs_create.topic.policy.class.name" href="#brokerconfigs_create.topic.policy.class.name">create.topic.policy.class.name</a></h4>
-<p>The create topic policy class that should be used for validation. The class should implement the <code>org.apache.kafka.server.policy.CreateTopicPolicy</code> interface. <p>Note: This policy runs on the controller instead of the broker.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="delegation.token.expiry.check.interval.ms"></a><a id="brokerconfigs_delegation.token.expiry.check.interval.ms" href="#brokerconfigs_delegation.token.expiry.check.interval.ms">delegation.token.expiry.check.interval.ms</a></h4>
-<p>Scan interval to remove expired delegation tokens.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="kafka.metrics.polling.interval.secs"></a><a id="brokerconfigs_kafka.metrics.polling.interval.secs" href="#brokerconfigs_kafka.metrics.polling.interval.secs">kafka.metrics.polling.interval.secs</a></h4>
-<p>The metrics polling interval (in seconds) which can be used in kafka.metrics.reporters implementations.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="kafka.metrics.reporters"></a><a id="brokerconfigs_kafka.metrics.reporters" href="#brokerconfigs_kafka.metrics.reporters">kafka.metrics.reporters</a></h4>
-<p>A list of classes to use as Yammer metrics custom reporters. The reporters should implement <code>kafka.metrics.KafkaMetricsReporter</code> trait. If a client wants to expose JMX operations on a custom reporter, the custom reporter needs to additionally implement an MBean trait that extends <code>kafka.metrics.KafkaMetricsReporterMBean</code> trait so that the registered MBean is compliant with the standard MBean convention.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="listener.security.protocol.map"></a><a id="brokerconfigs_listener.security.protocol.map" href="#brokerconfigs_listener.security.protocol.map">listener.security.protocol.map</a></h4>
-<p>Map between listener names and security protocols. This must be defined for the same security protocol to be usable in more than one port or IP. For example, internal and external traffic can be separated even if SSL is required for both. Concretely, the user could define listeners with names INTERNAL and EXTERNAL and this property as: <code>INTERNAL:SSL,EXTERNAL:SSL</code>. As shown, key and value are separated by a colon and map entries are separated by commas. Each listener name sh [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>SASL_SSL:SASL_SSL,PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="log.dir.failure.timeout.ms"></a><a id="brokerconfigs_log.dir.failure.timeout.ms" href="#brokerconfigs_log.dir.failure.timeout.ms">log.dir.failure.timeout.ms</a></h4>
-<p>If the broker is unable to successfully communicate to the controller that some log directory has failed for longer than this time, the broker will fail and shut down.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metadata.max.idle.interval.ms"></a><a id="brokerconfigs_metadata.max.idle.interval.ms" href="#brokerconfigs_metadata.max.idle.interval.ms">metadata.max.idle.interval.ms</a></h4>
-<p>This configuration controls how often the active controller should write no-op records to the metadata partition. If the value is 0, no-op records are not appended to the metadata partition. The default value is 500</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>500</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metric.reporters"></a><a id="brokerconfigs_metric.reporters" href="#brokerconfigs_metric.reporters">metric.reporters</a></h4>
-<p>A list of classes to use as metrics reporters. Implementing the <code>org.apache.kafka.common.metrics.MetricsReporter</code> interface allows plugging in classes that will be notified of new metric creation. When custom reporters are set and <code>org.apache.kafka.common.metrics.JmxReporter</code> is needed, it has to be explicitly added to the list.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.metrics.JmxReporter</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.num.samples"></a><a id="brokerconfigs_metrics.num.samples" href="#brokerconfigs_metrics.num.samples">metrics.num.samples</a></h4>
-<p>The number of samples maintained to compute metrics.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.recording.level"></a><a id="brokerconfigs_metrics.recording.level" href="#brokerconfigs_metrics.recording.level">metrics.recording.level</a></h4>
-<p>The highest recording level for metrics. It has three levels for recording metrics - info, debug, and trace.<br> <br>INFO level records only essential metrics necessary for monitoring system performance and health. It collects vital data without gathering too much detail, making it suitable for production environments where minimal overhead is desired.<br><br>DEBUG level records most metrics, providing more detailed information about the system's operation. It's useful for development [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>INFO</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metrics.sample.window.ms"></a><a id="brokerconfigs_metrics.sample.window.ms" href="#brokerconfigs_metrics.sample.window.ms">metrics.sample.window.ms</a></h4>
-<p>The window of time a metrics sample is computed over.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="producer.id.expiration.ms"></a><a id="brokerconfigs_producer.id.expiration.ms" href="#brokerconfigs_producer.id.expiration.ms">producer.id.expiration.ms</a></h4>
-<p>The time in ms that a topic partition leader will wait before expiring producer IDs. Producer IDs will not expire while a transaction associated to them is still ongoing. Note that producer IDs may expire sooner if the last write from the producer ID is deleted due to the topic's retention settings. Setting this value the same or higher than <code>delivery.timeout.ms</code> can help prevent expiration during retries and protect against message duplication, but the default should be re [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>86400000 (1 day)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="quota.window.num"></a><a id="brokerconfigs_quota.window.num" href="#brokerconfigs_quota.window.num">quota.window.num</a></h4>
-<p>The number of samples to retain in memory for client quotas</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>11</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="quota.window.size.seconds"></a><a id="brokerconfigs_quota.window.size.seconds" href="#brokerconfigs_quota.window.size.seconds">quota.window.size.seconds</a></h4>
-<p>The time span of each sample for client quotas</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.index.file.cache.total.size.bytes"></a><a id="brokerconfigs_remote.log.index.file.cache.total.size.bytes" href="#brokerconfigs_remote.log.index.file.cache.total.size.bytes">remote.log.index.file.cache.total.size.bytes</a></h4>
-<p>The total size of the space allocated to store index files fetched from remote storage in the local storage.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>1073741824 (1 gibibyte)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.manager.task.interval.ms"></a><a id="brokerconfigs_remote.log.manager.task.interval.ms" href="#brokerconfigs_remote.log.manager.task.interval.ms">remote.log.manager.task.interval.ms</a></h4>
-<p>Interval at which remote log manager runs the scheduled tasks like copy segments, and clean up remote log segments.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>30000 (30 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="remote.log.metadata.custom.metadata.max.bytes"></a><a id="brokerconfigs_remote.log.metadata.custom.metadata.max.bytes" href="#brokerconfigs_remote.log.metadata.custom.metadata.max.bytes">remote.log.metadata.custom.metadata.max.bytes</a></h4>
-<p>The maximum size of custom metadata in bytes that the broker should accept from a remote storage plugin. If custom metadata exceeds this limit, the updated segment metadata will not be stored, the copied data will be attempted to delete, and the remote copying task for this topic-partition will stop with an error.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>128</td></tr>
-<tr><th>Valid Values:</th><td>[0,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replication.quota.window.num"></a><a id="brokerconfigs_replication.quota.window.num" href="#brokerconfigs_replication.quota.window.num">replication.quota.window.num</a></h4>
-<p>The number of samples to retain in memory for replication quotas</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>11</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replication.quota.window.size.seconds"></a><a id="brokerconfigs_replication.quota.window.size.seconds" href="#brokerconfigs_replication.quota.window.size.seconds">replication.quota.window.size.seconds</a></h4>
-<p>The time span of each sample for replication quotas</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.connect.timeout.ms"></a><a id="brokerconfigs_sasl.login.connect.timeout.ms" href="#brokerconfigs_sasl.login.connect.timeout.ms">sasl.login.connect.timeout.ms</a></h4>
-<p>The (optional) value in milliseconds for the external authentication provider connection timeout. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.read.timeout.ms"></a><a id="brokerconfigs_sasl.login.read.timeout.ms" href="#brokerconfigs_sasl.login.read.timeout.ms">sasl.login.read.timeout.ms</a></h4>
-<p>The (optional) value in milliseconds for the external authentication provider read timeout. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.retry.backoff.max.ms"></a><a id="brokerconfigs_sasl.login.retry.backoff.max.ms" href="#brokerconfigs_sasl.login.retry.backoff.max.ms">sasl.login.retry.backoff.max.ms</a></h4>
-<p>The (optional) value in milliseconds for the maximum wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.retry.backoff.ms"></a><a id="brokerconfigs_sasl.login.retry.backoff.ms" href="#brokerconfigs_sasl.login.retry.backoff.ms">sasl.login.retry.backoff.ms</a></h4>
-<p>The (optional) value in milliseconds for the initial wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.exp.seconds"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.claim.exp.seconds" href="#brokerconfigs_sasl.oauthbearer.assertion.claim.exp.seconds">sasl.oauthbearer.assertion.claim.exp.seconds</a></h4>
-<p><p>The number of seconds <em>in the future</em> for which the JWT is valid. The value is used to determine the JWT <code>exp</code> (Expiration) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>exp</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> exp = x + y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbear [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,86400]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.nbf.seconds"></a><a id="brokerconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds" href="#brokerconfigs_sasl.oauthbearer.assertion.claim.nbf.seconds">sasl.oauthbearer.assertion.claim.nbf.seconds</a></h4>
-<p><p>The number of seconds <em>in the past</em> from which the JWT is valid. The value is used to determine the JWT <code>nbf</code> (Not Before) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>nbf</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> nbf = x - y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbeare [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.clock.skew.seconds"></a><a id="brokerconfigs_sasl.oauthbearer.clock.skew.seconds" href="#brokerconfigs_sasl.oauthbearer.clock.skew.seconds">sasl.oauthbearer.clock.skew.seconds</a></h4>
-<p>The (optional) value in seconds to allow for differences between the time of the OAuth/OIDC identity provider and the broker.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.expected.audience"></a><a id="brokerconfigs_sasl.oauthbearer.expected.audience" href="#brokerconfigs_sasl.oauthbearer.expected.audience">sasl.oauthbearer.expected.audience</a></h4>
-<p>The (optional) comma-delimited setting for the broker to use to verify that the JWT was issued for one of the expected audiences. The JWT will be inspected for the standard OAuth "aud" claim and if this value is set, the broker will match the value from JWT's "aud" claim to see if there is an exact match. If there is no match, the broker will reject the JWT and authentication will fail.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.expected.issuer"></a><a id="brokerconfigs_sasl.oauthbearer.expected.issuer" href="#brokerconfigs_sasl.oauthbearer.expected.issuer">sasl.oauthbearer.expected.issuer</a></h4>
-<p>The (optional) setting for the broker to use to verify that the JWT was created by the expected issuer. The JWT will be inspected for the standard OAuth "iss" claim and if this value is set, the broker will match it exactly against what is in the JWT's "iss" claim. If there is no match, the broker will reject the JWT and authentication will fail.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.refresh.ms"></a><a id="brokerconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms" href="#brokerconfigs_sasl.oauthbearer.jwks.endpoint.refresh.ms">sasl.oauthbearer.jwks.endpoint.refresh.ms</a></h4>
-<p>The (optional) value in milliseconds for the broker to wait between refreshing its JWKS (JSON Web Key Set) cache that contains the keys to verify the signature of the JWT.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms"></a><a id="brokerconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms" href="#brokerconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms</a></h4>
-<p>The (optional) value in milliseconds for the maximum wait between attempts to retrieve the JWKS (JSON Web Key Set) from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.ms"></a><a id="brokerconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms" href="#brokerconfigs_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.ms</a></h4>
-<p>The (optional) value in milliseconds for the initial wait between JWKS (JSON Web Key Set) retrieval attempts from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.scope.claim.name"></a><a id="brokerconfigs_sasl.oauthbearer.scope.claim.name" href="#brokerconfigs_sasl.oauthbearer.scope.claim.name">sasl.oauthbearer.scope.claim.name</a></h4>
-<p>The OAuth claim for the scope is often named "scope", but this (optional) setting can provide a different name to use for the scope included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>scope</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.sub.claim.name"></a><a id="brokerconfigs_sasl.oauthbearer.sub.claim.name" href="#brokerconfigs_sasl.oauthbearer.sub.claim.name">sasl.oauthbearer.sub.claim.name</a></h4>
-<p>The OAuth claim for the subject is often named "sub", but this (optional) setting can provide a different name to use for the subject included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>sub</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="security.providers"></a><a id="brokerconfigs_security.providers" href="#brokerconfigs_security.providers">security.providers</a></h4>
-<p>A list of configurable creator classes each returning a provider implementing security algorithms. These classes should implement the <code>org.apache.kafka.common.security.auth.SecurityProviderCreator</code> interface.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.allow.dn.changes"></a><a id="brokerconfigs_ssl.allow.dn.changes" href="#brokerconfigs_ssl.allow.dn.changes">ssl.allow.dn.changes</a></h4>
-<p>Indicates whether changes to the certificate distinguished name should be allowed during a dynamic reconfiguration of certificates or not.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.allow.san.changes"></a><a id="brokerconfigs_ssl.allow.san.changes" href="#brokerconfigs_ssl.allow.san.changes">ssl.allow.san.changes</a></h4>
-<p>Indicates whether changes to the certificate subject alternative names should be allowed during a dynamic reconfiguration of certificates or not.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.endpoint.identification.algorithm"></a><a id="brokerconfigs_ssl.endpoint.identification.algorithm" href="#brokerconfigs_ssl.endpoint.identification.algorithm">ssl.endpoint.identification.algorithm</a></h4>
-<p>The endpoint identification algorithm to validate server hostname using server certificate. </p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>https</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.engine.factory.class"></a><a id="brokerconfigs_ssl.engine.factory.class" href="#brokerconfigs_ssl.engine.factory.class">ssl.engine.factory.class</a></h4>
-<p>The class of type org.apache.kafka.common.security.auth.SslEngineFactory to provide SSLEngine objects. Default value is org.apache.kafka.common.security.ssl.DefaultSslEngineFactory. Alternatively, setting this to org.apache.kafka.common.security.ssl.CommonNameLoggingSslEngineFactory will log the common name of expired SSL certificates used by clients to authenticate at any of the brokers with log level INFO. Note that this will cause a tiny delay during establishment of new connection [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.principal.mapping.rules"></a><a id="brokerconfigs_ssl.principal.mapping.rules" href="#brokerconfigs_ssl.principal.mapping.rules">ssl.principal.mapping.rules</a></h4>
-<p>A list of rules for mapping from distinguished name from the client certificate to short name. The rules are evaluated in order and the first rule that matches a principal name is used to map it to a short name. Any later rules in the list are ignored. By default, distinguished name of the X.500 certificate will be the principal. For more details on the format please see <a href="#security_authz"> security authorization and acls</a>. Note that this configuration is ignored if an exten [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>DEFAULT</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.secure.random.implementation"></a><a id="brokerconfigs_ssl.secure.random.implementation" href="#brokerconfigs_ssl.secure.random.implementation">ssl.secure.random.implementation</a></h4>
-<p>The SecureRandom PRNG implementation to use for SSL cryptography operations. </p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>per-broker</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="telemetry.max.bytes"></a><a id="brokerconfigs_telemetry.max.bytes" href="#brokerconfigs_telemetry.max.bytes">telemetry.max.bytes</a></h4>
-<p>The maximum size (after compression if compression is used) of telemetry metrics pushed from a client to the broker. The default value is 1048576 (1 MB).</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1048576 (1 mebibyte)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transaction.abort.timed.out.transaction.cleanup.interval.ms"></a><a id="brokerconfigs_transaction.abort.timed.out.transaction.cleanup.interval.ms" href="#brokerconfigs_transaction.abort.timed.out.transaction.cleanup.interval.ms">transaction.abort.timed.out.transaction.cleanup.interval.ms</a></h4>
-<p>The interval at which to rollback transactions that have timed out</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transaction.partition.verification.enable"></a><a id="brokerconfigs_transaction.partition.verification.enable" href="#brokerconfigs_transaction.partition.verification.enable">transaction.partition.verification.enable</a></h4>
-<p>Enable verification that checks that the partition has been added to the transaction before writing transactional records to the partition</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>cluster-wide</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transaction.remove.expired.transaction.cleanup.interval.ms"></a><a id="brokerconfigs_transaction.remove.expired.transaction.cleanup.interval.ms" href="#brokerconfigs_transaction.remove.expired.transaction.cleanup.interval.ms">transaction.remove.expired.transaction.cleanup.interval.ms</a></h4>
-<p>The interval at which to remove transactions that have expired due to <code>transactional.id.expiration.ms</code> passing</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transaction.two.phase.commit.enable"></a><a id="brokerconfigs_transaction.two.phase.commit.enable" href="#brokerconfigs_transaction.two.phase.commit.enable">transaction.two.phase.commit.enable</a></h4>
-<p>Allow participation in Two-Phase Commit (2PC) transactions with an external transaction coordinator</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-<tr><th>Update Mode:</th><td>read-only</td></tr>
-</tbody></table>
-</li>
-</ul>
-
diff --git a/content/en/43/generated/mirror_checkpoint_config.html b/content/en/43/generated/mirror_checkpoint_config.html
index cd53f9c1ea..e69de29bb2 100644
--- a/content/en/43/generated/mirror_checkpoint_config.html
+++ b/content/en/43/generated/mirror_checkpoint_config.html
@@ -1,143 +0,0 @@
-<ul class="config-list">
-<li>
-<h4><a id="groups"></a><a id="mirror_checkpoint_groups" href="#mirror_checkpoint_groups">groups</a></h4>
-<p>Consumer groups to replicate. Supports comma-separated group IDs and regexes.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>.*</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="groups.exclude"></a><a id="mirror_checkpoint_groups.exclude" href="#mirror_checkpoint_groups.exclude">groups.exclude</a></h4>
-<p>Exclude groups. Supports comma-separated group IDs and regexes. Excludes take precedence over includes.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>console-consumer-.*,connect-.*,__.*</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="checkpoints.topic.replication.factor"></a><a id="mirror_checkpoint_checkpoints.topic.replication.factor" href="#mirror_checkpoint_checkpoints.topic.replication.factor">checkpoints.topic.replication.factor</a></h4>
-<p>Replication factor for checkpoints topic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="consumer.poll.timeout.ms"></a><a id="mirror_checkpoint_consumer.poll.timeout.ms" href="#mirror_checkpoint_consumer.poll.timeout.ms">consumer.poll.timeout.ms</a></h4>
-<p>Timeout when polling source cluster.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="emit.checkpoints.enabled"></a><a id="mirror_checkpoint_emit.checkpoints.enabled" href="#mirror_checkpoint_emit.checkpoints.enabled">emit.checkpoints.enabled</a></h4>
-<p>Whether to replicate consumer offsets to target cluster.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="emit.checkpoints.interval.seconds"></a><a id="mirror_checkpoint_emit.checkpoints.interval.seconds" href="#mirror_checkpoint_emit.checkpoints.interval.seconds">emit.checkpoints.interval.seconds</a></h4>
-<p>Frequency of checkpoints.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="group.filter.class"></a><a id="mirror_checkpoint_group.filter.class" href="#mirror_checkpoint_group.filter.class">group.filter.class</a></h4>
-<p>GroupFilter to use. Selects consumer groups to replicate.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.connect.mirror.DefaultGroupFilter</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metric.names.formats"></a><a id="mirror_checkpoint_metric.names.formats" href="#mirror_checkpoint_metric.names.formats">metric.names.formats</a></h4>
-<p>Deprecated. The formats in which metrics are emitted. Valid values are legacy and new. When set to legacy, the metrics have the following name "kafka.connect.mirror:type=MirrorCheckpointConnector,source={SOURCE},target={TARGET},group={GROUP},topic={TOPIC},partition={PARTITION}". When set to new, the metrics have the following name "kafka.connect:type=plugins,connector={CONNECTOR},task={TASK},source={SOURCE},target={TARGET},group={GROUP},topic={TOPIC},partition={PARTITION}". When set t [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>legacy</td></tr>
-<tr><th>Valid Values:</th><td>[legacy, new]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offset-syncs.topic.location"></a><a id="mirror_checkpoint_offset-syncs.topic.location" href="#mirror_checkpoint_offset-syncs.topic.location">offset-syncs.topic.location</a></h4>
-<p>The location (source/target) of the offset-syncs topic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>source</td></tr>
-<tr><th>Valid Values:</th><td>[source, target]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="refresh.groups.enabled"></a><a id="mirror_checkpoint_refresh.groups.enabled" href="#mirror_checkpoint_refresh.groups.enabled">refresh.groups.enabled</a></h4>
-<p>Whether to periodically check for new consumer groups.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="refresh.groups.interval.seconds"></a><a id="mirror_checkpoint_refresh.groups.interval.seconds" href="#mirror_checkpoint_refresh.groups.interval.seconds">refresh.groups.interval.seconds</a></h4>
-<p>Frequency of group refresh.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>600</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sync.group.offsets.enabled"></a><a id="mirror_checkpoint_sync.group.offsets.enabled" href="#mirror_checkpoint_sync.group.offsets.enabled">sync.group.offsets.enabled</a></h4>
-<p>Whether to periodically write the translated offsets to __consumer_offsets topic in target cluster, as long as no active consumers in that group are connected to the target cluster</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sync.group.offsets.interval.seconds"></a><a id="mirror_checkpoint_sync.group.offsets.interval.seconds" href="#mirror_checkpoint_sync.group.offsets.interval.seconds">sync.group.offsets.interval.seconds</a></h4>
-<p>Frequency of consumer group offset sync.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="topic.filter.class"></a><a id="mirror_checkpoint_topic.filter.class" href="#mirror_checkpoint_topic.filter.class">topic.filter.class</a></h4>
-<p>TopicFilter to use. Selects topics to replicate.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.connect.mirror.DefaultTopicFilter</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-</ul>
-
diff --git a/content/en/43/generated/mirror_connector_config.html b/content/en/43/generated/mirror_connector_config.html
index a6a09bb0b5..e69de29bb2 100644
--- a/content/en/43/generated/mirror_connector_config.html
+++ b/content/en/43/generated/mirror_connector_config.html
@@ -1,943 +0,0 @@
-<ul class="config-list">
-<li>
-<h4><a id="source.cluster.alias"></a><a id="mirror_connector_source.cluster.alias" href="#mirror_connector_source.cluster.alias">source.cluster.alias</a></h4>
-<p>Alias of source cluster</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.key.password"></a><a id="mirror_connector_ssl.key.password" href="#mirror_connector_ssl.key.password">ssl.key.password</a></h4>
-<p>The password of the private key in the key store file or the PEM key specified in 'ssl.keystore.key'.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.certificate.chain"></a><a id="mirror_connector_ssl.keystore.certificate.chain" href="#mirror_connector_ssl.keystore.certificate.chain">ssl.keystore.certificate.chain</a></h4>
-<p>Certificate chain in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with a list of X.509 certificates</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.key"></a><a id="mirror_connector_ssl.keystore.key" href="#mirror_connector_ssl.keystore.key">ssl.keystore.key</a></h4>
-<p>Private key in the format specified by 'ssl.keystore.type'. Default SSL engine factory supports only PEM format with PKCS#8 keys. If the key is encrypted, key password must be specified using 'ssl.key.password'</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.location"></a><a id="mirror_connector_ssl.keystore.location" href="#mirror_connector_ssl.keystore.location">ssl.keystore.location</a></h4>
-<p>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.password"></a><a id="mirror_connector_ssl.keystore.password" href="#mirror_connector_ssl.keystore.password">ssl.keystore.password</a></h4>
-<p>The store password for the key store file. This is optional for client and only needed if 'ssl.keystore.location' is configured. Key store password is not supported for PEM format.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.certificates"></a><a id="mirror_connector_ssl.truststore.certificates" href="#mirror_connector_ssl.truststore.certificates">ssl.truststore.certificates</a></h4>
-<p>Trusted certificates in the format specified by 'ssl.truststore.type'. Default SSL engine factory supports only PEM format with X.509 certificates.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.location"></a><a id="mirror_connector_ssl.truststore.location" href="#mirror_connector_ssl.truststore.location">ssl.truststore.location</a></h4>
-<p>The location of the trust store file.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.password"></a><a id="mirror_connector_ssl.truststore.password" href="#mirror_connector_ssl.truststore.password">ssl.truststore.password</a></h4>
-<p>The password for the trust store file. If a password is not set, trust store file configured will still be used, but integrity checking is disabled. Trust store password is not supported for PEM format.</p>
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="target.cluster.alias"></a><a id="mirror_connector_target.cluster.alias" href="#mirror_connector_target.cluster.alias">target.cluster.alias</a></h4>
-<p>Alias of target cluster. Used in metrics reporting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>target</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.client.callback.handler.class"></a><a id="mirror_connector_sasl.client.callback.handler.class" href="#mirror_connector_sasl.client.callback.handler.class">sasl.client.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL client callback handler class that implements the AuthenticateCallbackHandler interface.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.jaas.config"></a><a id="mirror_connector_sasl.jaas.config" href="#mirror_connector_sasl.jaas.config">sasl.jaas.config</a></h4>
-<p>JAAS login context parameters for SASL connections in the format used by JAAS configuration files. JAAS configuration file format is described <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html">here</a>. The format for the value is: <code>loginModuleClass controlFlag (optionName=optionValue)*;</code>. For brokers, the config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.service.name"></a><a id="mirror_connector_sasl.kerberos.service.name" href="#mirror_connector_sasl.kerberos.service.name">sasl.kerberos.service.name</a></h4>
-<p>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.callback.handler.class"></a><a id="mirror_connector_sasl.login.callback.handler.class" href="#mirror_connector_sasl.login.callback.handler.class">sasl.login.callback.handler.class</a></h4>
-<p>The fully qualified name of a SASL login callback handler class that implements the AuthenticateCallbackHandler interface. For brokers, login callback handler config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.callback.handler.class=com.example.CustomScramLoginCallbackHandler</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.class"></a><a id="mirror_connector_sasl.login.class" href="#mirror_connector_sasl.login.class">sasl.login.class</a></h4>
-<p>The fully qualified name of a class that implements the Login interface. For brokers, login config must be prefixed with listener prefix and SASL mechanism name in lower-case. For example, listener.name.sasl_ssl.scram-sha-256.sasl.login.class=com.example.CustomScramLogin</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.mechanism"></a><a id="mirror_connector_sasl.mechanism" href="#mirror_connector_sasl.mechanism">sasl.mechanism</a></h4>
-<p>SASL mechanism used for client connections. This may be any mechanism for which a security provider is available. GSSAPI is the default mechanism.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>GSSAPI</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.algorithm"></a><a id="mirror_connector_sasl.oauthbearer.assertion.algorithm" href="#mirror_connector_sasl.oauthbearer.assertion.algorithm">sasl.oauthbearer.assertion.algorithm</a></h4>
-<p><p>The algorithm the Apache Kafka client should use to sign the assertion sent to the identity provider. It is also used as the value of the OAuth <code>alg</code> (Algorithm) header in the JWT assertion.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>RS256</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [ES256, RS256]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.aud"></a><a id="mirror_connector_sasl.oauthbearer.assertion.claim.aud" href="#mirror_connector_sasl.oauthbearer.assertion.claim.aud">sasl.oauthbearer.assertion.claim.aud</a></h4>
-<p><p>The JWT <code>aud</code> (Audience) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.iss"></a><a id="mirror_connector_sasl.oauthbearer.assertion.claim.iss" href="#mirror_connector_sasl.oauthbearer.assertion.claim.iss">sasl.oauthbearer.assertion.claim.iss</a></h4>
-<p><p>The value to be used as the <code>iss</code> (Issuer) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.jti.include"></a><a id="mirror_connector_sasl.oauthbearer.assertion.claim.jti.include" href="#mirror_connector_sasl.oauthbearer.assertion.claim.jti.include">sasl.oauthbearer.assertion.claim.jti.include</a></h4>
-<p><p>Flag that determines if the JWT assertion should generate a unique ID for the JWT and include it in the <code>jti</code> (JWT ID) claim.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.sub"></a><a id="mirror_connector_sasl.oauthbearer.assertion.claim.sub" href="#mirror_connector_sasl.oauthbearer.assertion.claim.sub">sasl.oauthbearer.assertion.claim.sub</a></h4>
-<p><p>The value to be used as the <code>sub</code> (Subject) claim which will be included in the client JWT assertion created locally.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.assertion.file</code> is provided, this configuration will be ignored.</p></p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.file"></a><a id="mirror_connector_sasl.oauthbearer.assertion.file" href="#mirror_connector_sasl.oauthbearer.assertion.file">sasl.oauthbearer.assertion.file</a></h4>
-<p><p>File that contains a <em>pre-generated</em> JWT assertion.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect whenthe file changes to allow for the file to be reloaded on modifications. This allows for "live" assertion rotation without restarting the Kafka client.</p><p>The file contains the assertion in the serialized, three part JWT format:</p><ol><li>The <em>hea [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.private.key.file"></a><a id="mirror_connector_sasl.oauthbearer.assertion.private.key.file" href="#mirror_connector_sasl.oauthbearer.assertion.private.key.file">sasl.oauthbearer.assertion.private.key.file</a></h4>
-<p><p>File that contains a private key in the standard PEM format which is used to sign the JWT assertion sent to the identity provider.</p><p>The underlying implementation caches the file contents to avoid the performance hit of loading the file on each access. The caching mechanism will detect when the file changes to allow for the file to be reloaded on modifications. This allows for "live" private key rotation without restarting the Kafka client.</p><p><em>Note</em>: If a v [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.private.key.passphrase"></a><a id="mirror_connector_sasl.oauthbearer.assertion.private.key.passphrase" href="#mirror_connector_sasl.oauthbearer.assertion.private.key.passphrase">sasl.oauthbearer.assertion.private.key.passphrase</a></h4>
-<p><p>The optional passphrase to decrypt the private key file specified by <code>sasl.oauthbearer.assertion.private.key.file</code>.</p><p><em>Note</em>: If the file referred to by <code>sasl.oauthbearer.assertion.private.key.file</code> is modified on the file system at runtime and it was created with a <em>different</em> passphrase than it was previously, the client will not be able to access the private key file because the passphrase is now out of date. For that reason, when using pr [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.template.file"></a><a id="mirror_connector_sasl.oauthbearer.assertion.template.file" href="#mirror_connector_sasl.oauthbearer.assertion.template.file">sasl.oauthbearer.assertion.template.file</a></h4>
-<p><p>This optional configuration specifies the file containing the JWT headers and/or payload claims to be used when creating the JWT assertion.</p><p>Not all identity providers require the same set of claims; some may require a given claim while others may prohibit it. In order to provide the most flexibility, this configuration allows the user to provide the static header values and claims that are to be included in the JWT.</p><p><em>Note</em>: If a value for <code>sasl.oauthbearer.a [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.client.credentials.client.id"></a><a id="mirror_connector_sasl.oauthbearer.client.credentials.client.id" href="#mirror_connector_sasl.oauthbearer.client.credentials.client.id">sasl.oauthbearer.client.credentials.client.id</a></h4>
-<p><p>The ID (defined in/by the OAuth identity provider) to identify the client requesting the token.</p><p>The client ID was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientId</code>. For backward compatibility, the <code>clientId</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.client.credentials.client.id</code> from conf [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.client.credentials.client.secret"></a><a id="mirror_connector_sasl.oauthbearer.client.credentials.client.secret" href="#mirror_connector_sasl.oauthbearer.client.credentials.client.secret">sasl.oauthbearer.client.credentials.client.secret</a></h4>
-<p><p>The secret (defined by either the user or preassigned, depending on the identity provider) of the client requesting the token.</p><p>The client secret was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>clientSecret</code>. For backward compatibility, the <code>clientSecret</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p>Order of precedence:</p><ul><li><code>sasl.oauthbearer.cl [...]
-<table><tbody>
-<tr><th>Type:</th><td>password</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.url"></a><a id="mirror_connector_sasl.oauthbearer.jwks.endpoint.url" href="#mirror_connector_sasl.oauthbearer.jwks.endpoint.url">sasl.oauthbearer.jwks.endpoint.url</a></h4>
-<p>The OAuth/OIDC provider URL from which the provider's <a href="https://datatracker.ietf.org/doc/html/rfc7517#section-5">JWKS (JSON Web Key Set)</a> can be retrieved. The URL can be HTTP(S)-based or file-based. If the URL is HTTP(S)-based, the JWKS data will be retrieved from the OAuth/OIDC provider via the configured URL on broker startup. All then-current keys will be cached on the broker for incoming requests. If an authentication request is received for a JWT that includes a "kid" [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwt.retriever.class"></a><a id="mirror_connector_sasl.oauthbearer.jwt.retriever.class" href="#mirror_connector_sasl.oauthbearer.jwt.retriever.class">sasl.oauthbearer.jwt.retriever.class</a></h4>
-<p><p>The fully-qualified class name of a <code>JwtRetriever</code> implementation used to request tokens from the identity provider.</p><p>The default configuration value represents a class that maintains backward compatibility with previous versions of Apache Kafka. The default implementation uses the configuration to determine which concrete implementation to create.<p>Other implementations that are provided include:</p><ul><li><code>org.apache.kafka.common.security.oauthbearer.Client [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtRetriever</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwt.validator.class"></a><a id="mirror_connector_sasl.oauthbearer.jwt.validator.class" href="#mirror_connector_sasl.oauthbearer.jwt.validator.class">sasl.oauthbearer.jwt.validator.class</a></h4>
-<p><p>The fully-qualified class name of a <code>JwtValidator</code> implementation used to validate the JWT from the identity provider.</p><p>The default validator (<code>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</code>) maintains backward compatibility with previous versions of Apache Kafka. The default validator uses configuration to determine which concrete implementation to create.<p>The built-in <code>JwtValidator</code> implementations are:</p><ul><li><code>o [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.scope"></a><a id="mirror_connector_sasl.oauthbearer.scope" href="#mirror_connector_sasl.oauthbearer.scope">sasl.oauthbearer.scope</a></h4>
-<p><p>This is the level of access a client application is granted to a resource or API which is included in the token request. If provided, it should match one or more scopes configured in the identity provider.</p><p>The scope was previously stored as part of the <code>sasl.jaas.config</code> configuration with the key <code>scope</code>. For backward compatibility, the <code>scope</code> JAAS option can still be used, but it is deprecated and will be removed in a future version.</p><p> [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.token.endpoint.url"></a><a id="mirror_connector_sasl.oauthbearer.token.endpoint.url" href="#mirror_connector_sasl.oauthbearer.token.endpoint.url">sasl.oauthbearer.token.endpoint.url</a></h4>
-<p>The URL for the OAuth/OIDC identity provider. If the URL is HTTP(S)-based, it is the issuer's token endpoint URL to which requests will be made to login based on the configuration in <code>sasl.oauthbearer.jwt.retriever.class</code>. If the URL is file-based, it specifies a file containing an access token (in JWT serialized form) issued by the OAuth/OIDC identity provider to use for authorization.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="security.protocol"></a><a id="mirror_connector_security.protocol" href="#mirror_connector_security.protocol">security.protocol</a></h4>
-<p>Protocol used to communicate with brokers.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>PLAINTEXT</td></tr>
-<tr><th>Valid Values:</th><td>(case insensitive) [SASL_SSL, PLAINTEXT, SSL, SASL_PLAINTEXT]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.enabled.protocols"></a><a id="mirror_connector_ssl.enabled.protocols" href="#mirror_connector_ssl.enabled.protocols">ssl.enabled.protocols</a></h4>
-<p>The list of protocols enabled for SSL connections. The default is 'TLSv1.2,TLSv1.3'. This means that clients and servers will prefer TLSv1.3 if both support it and fallback to TLSv1.2 otherwise (assuming both support at least TLSv1.2). This default should be fine for most use cases. If this configuration is set to an empty list, Kafka will use the protocols enabled by default in the underlying SSLEngine, which may include additional protocols depending on the JVM version. Also see the [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>TLSv1.2,TLSv1.3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keystore.type"></a><a id="mirror_connector_ssl.keystore.type" href="#mirror_connector_ssl.keystore.type">ssl.keystore.type</a></h4>
-<p>The file format of the key store file. This is optional for client. The values currently supported by the default <code>ssl.engine.factory.class</code> are [JKS, PKCS12, PEM].</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>JKS</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.protocol"></a><a id="mirror_connector_ssl.protocol" href="#mirror_connector_ssl.protocol">ssl.protocol</a></h4>
-<p>The SSL protocol used to generate the SSLContext. The default is 'TLSv1.3', which should be fine for most use cases. A typical alternative to the default is 'TLSv1.2'. Allowed values for this config are dependent on the JVM. Clients using the defaults for this config and 'ssl.enabled.protocols' will downgrade to 'TLSv1.2' if the server does not support 'TLSv1.3'. If this config is set to 'TLSv1.2', however, clients will not use 'TLSv1.3' even if it is one of the values in <code>ssl.en [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>TLSv1.3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.provider"></a><a id="mirror_connector_ssl.provider" href="#mirror_connector_ssl.provider">ssl.provider</a></h4>
-<p>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.truststore.type"></a><a id="mirror_connector_ssl.truststore.type" href="#mirror_connector_ssl.truststore.type">ssl.truststore.type</a></h4>
-<p>The file format of the trust store file. The values currently supported by the default <code>ssl.engine.factory.class</code> are [JKS, PKCS12, PEM].</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>JKS</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="admin.timeout.ms"></a><a id="mirror_connector_admin.timeout.ms" href="#mirror_connector_admin.timeout.ms">admin.timeout.ms</a></h4>
-<p>Timeout for administrative tasks, e.g. detecting new topics.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="config.providers"></a><a id="mirror_connector_config.providers" href="#mirror_connector_config.providers">config.providers</a></h4>
-<p>Comma-separated alias names for classes implementing the <code>ConfigProvider</code> interface. This enables loading configuration data (such as passwords, API keys, and other credentials) from external sources. For example, see <a href="https://kafka.apache.org/documentation/#config_providers">Configuration Providers</a>.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="enabled"></a><a id="mirror_connector_enabled" href="#mirror_connector_enabled">enabled</a></h4>
-<p>Whether to replicate source->target.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="forwarding.admin.class"></a><a id="mirror_connector_forwarding.admin.class" href="#mirror_connector_forwarding.admin.class">forwarding.admin.class</a></h4>
-<p>Class which extends ForwardingAdmin to define custom cluster resource management (topics, configs, etc). The class must have a constructor with signature <code>(Map<String, Object> config)</code> that is used to configure a KafkaAdminClient and may also be used to configure clients for external systems if necessary.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.clients.admin.ForwardingAdmin</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metric.reporters"></a><a id="mirror_connector_metric.reporters" href="#mirror_connector_metric.reporters">metric.reporters</a></h4>
-<p>A list of classes to use as metrics reporters. Implementing the <code>org.apache.kafka.common.metrics.MetricsReporter</code> interface allows plugging in classes that will be notified of new metric creation. When custom reporters are set and <code>org.apache.kafka.common.metrics.JmxReporter</code> is needed, it has to be explicitly added to the list.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.common.metrics.JmxReporter</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replication.policy.class"></a><a id="mirror_connector_replication.policy.class" href="#mirror_connector_replication.policy.class">replication.policy.class</a></h4>
-<p>Class which defines the remote topic naming convention.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.connect.mirror.DefaultReplicationPolicy</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replication.policy.internal.topic.separator.enabled"></a><a id="mirror_connector_replication.policy.internal.topic.separator.enabled" href="#mirror_connector_replication.policy.internal.topic.separator.enabled">replication.policy.internal.topic.separator.enabled</a></h4>
-<p>Whether to use replication.policy.separator to control the names of topics used for checkpoints and offset syncs. By default, custom separators are used in these topic names; however, if upgrading MirrorMaker 2 from older versions that did not allow for these topic names to be customized, it may be necessary to set this property to 'false' in order to continue using the same names for those topics.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replication.policy.separator"></a><a id="mirror_connector_replication.policy.separator" href="#mirror_connector_replication.policy.separator">replication.policy.separator</a></h4>
-<p>Separator used in remote topic naming convention.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>.</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.kinit.cmd"></a><a id="mirror_connector_sasl.kerberos.kinit.cmd" href="#mirror_connector_sasl.kerberos.kinit.cmd">sasl.kerberos.kinit.cmd</a></h4>
-<p>Kerberos kinit command path.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>/usr/bin/kinit</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.min.time.before.relogin"></a><a id="mirror_connector_sasl.kerberos.min.time.before.relogin" href="#mirror_connector_sasl.kerberos.min.time.before.relogin">sasl.kerberos.min.time.before.relogin</a></h4>
-<p>Login thread sleep time between refresh attempts.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60000</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.ticket.renew.jitter"></a><a id="mirror_connector_sasl.kerberos.ticket.renew.jitter" href="#mirror_connector_sasl.kerberos.ticket.renew.jitter">sasl.kerberos.ticket.renew.jitter</a></h4>
-<p>Percentage of random jitter added to the renewal time.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.05</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.kerberos.ticket.renew.window.factor"></a><a id="mirror_connector_sasl.kerberos.ticket.renew.window.factor" href="#mirror_connector_sasl.kerberos.ticket.renew.window.factor">sasl.kerberos.ticket.renew.window.factor</a></h4>
-<p>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.8</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.connect.timeout.ms"></a><a id="mirror_connector_sasl.login.connect.timeout.ms" href="#mirror_connector_sasl.login.connect.timeout.ms">sasl.login.connect.timeout.ms</a></h4>
-<p>The (optional) value in milliseconds for the external authentication provider connection timeout. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.read.timeout.ms"></a><a id="mirror_connector_sasl.login.read.timeout.ms" href="#mirror_connector_sasl.login.read.timeout.ms">sasl.login.read.timeout.ms</a></h4>
-<p>The (optional) value in milliseconds for the external authentication provider read timeout. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.buffer.seconds"></a><a id="mirror_connector_sasl.login.refresh.buffer.seconds" href="#mirror_connector_sasl.login.refresh.buffer.seconds">sasl.login.refresh.buffer.seconds</a></h4>
-<p>The amount of buffer time before credential expiration to maintain when refreshing a credential, in seconds. If a refresh would otherwise occur closer to expiration than the number of buffer seconds then the refresh will be moved up to maintain as much of the buffer time as possible. Legal values are between 0 and 3600 (1 hour); a default value of 300 (5 minutes) is used if no value is specified. This value and sasl.login.refresh.min.period.seconds are both ignored if their sum excee [...]
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.min.period.seconds"></a><a id="mirror_connector_sasl.login.refresh.min.period.seconds" href="#mirror_connector_sasl.login.refresh.min.period.seconds">sasl.login.refresh.min.period.seconds</a></h4>
-<p>The desired minimum time for the login refresh thread to wait before refreshing a credential, in seconds. Legal values are between 0 and 900 (15 minutes); a default value of 60 (1 minute) is used if no value is specified. This value and sasl.login.refresh.buffer.seconds are both ignored if their sum exceeds the remaining lifetime of a credential. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,900]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.window.factor"></a><a id="mirror_connector_sasl.login.refresh.window.factor" href="#mirror_connector_sasl.login.refresh.window.factor">sasl.login.refresh.window.factor</a></h4>
-<p>Login refresh thread will sleep until the specified window factor relative to the credential's lifetime has been reached, at which time it will try to refresh the credential. Legal values are between 0.5 (50%) and 1.0 (100%) inclusive; a default value of 0.8 (80%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.8</td></tr>
-<tr><th>Valid Values:</th><td>[0.5,...,1.0]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.refresh.window.jitter"></a><a id="mirror_connector_sasl.login.refresh.window.jitter" href="#mirror_connector_sasl.login.refresh.window.jitter">sasl.login.refresh.window.jitter</a></h4>
-<p>The maximum amount of random jitter relative to the credential's lifetime that is added to the login refresh thread's sleep time. Legal values are between 0 and 0.25 (25%) inclusive; a default value of 0.05 (5%) is used if no value is specified. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>double</td></tr>
-<tr><th>Default:</th><td>0.05</td></tr>
-<tr><th>Valid Values:</th><td>[0.0,...,0.25]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.retry.backoff.max.ms"></a><a id="mirror_connector_sasl.login.retry.backoff.max.ms" href="#mirror_connector_sasl.login.retry.backoff.max.ms">sasl.login.retry.backoff.max.ms</a></h4>
-<p>The (optional) value in milliseconds for the maximum wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.login.retry.backoff.ms"></a><a id="mirror_connector_sasl.login.retry.backoff.ms" href="#mirror_connector_sasl.login.retry.backoff.ms">sasl.login.retry.backoff.ms</a></h4>
-<p>The (optional) value in milliseconds for the initial wait between login attempts to the external authentication provider. Login uses an exponential backoff algorithm with an initial wait based on the sasl.login.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.login.retry.backoff.max.ms setting. Currently applies only to OAUTHBEARER.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.exp.seconds"></a><a id="mirror_connector_sasl.oauthbearer.assertion.claim.exp.seconds" href="#mirror_connector_sasl.oauthbearer.assertion.claim.exp.seconds">sasl.oauthbearer.assertion.claim.exp.seconds</a></h4>
-<p><p>The number of seconds <em>in the future</em> for which the JWT is valid. The value is used to determine the JWT <code>exp</code> (Expiration) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>exp</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> exp = x + y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbear [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>300</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,86400]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.assertion.claim.nbf.seconds"></a><a id="mirror_connector_sasl.oauthbearer.assertion.claim.nbf.seconds" href="#mirror_connector_sasl.oauthbearer.assertion.claim.nbf.seconds">sasl.oauthbearer.assertion.claim.nbf.seconds</a></h4>
-<p><p>The number of seconds <em>in the past</em> from which the JWT is valid. The value is used to determine the JWT <code>nbf</code> (Not Before) claim based on the current system time when the JWT is created.</p><p>The formula to generate the <code>nbf</code> claim is very simple:</p><pre>Let:<br><br> x = the current timestamp in seconds, on client<br> y = the value of this configuration<br><br>Then:<br><br> nbf = x - y<br></pre><p><em>Note</em>: If a value for <code>sasl.oauthbeare [...]
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>60</td></tr>
-<tr><th>Valid Values:</th><td>[0,...,3600]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.clock.skew.seconds"></a><a id="mirror_connector_sasl.oauthbearer.clock.skew.seconds" href="#mirror_connector_sasl.oauthbearer.clock.skew.seconds">sasl.oauthbearer.clock.skew.seconds</a></h4>
-<p>The (optional) value in seconds to allow for differences between the time of the OAuth/OIDC identity provider and the broker.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>30</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.expected.audience"></a><a id="mirror_connector_sasl.oauthbearer.expected.audience" href="#mirror_connector_sasl.oauthbearer.expected.audience">sasl.oauthbearer.expected.audience</a></h4>
-<p>The (optional) comma-delimited setting for the broker to use to verify that the JWT was issued for one of the expected audiences. The JWT will be inspected for the standard OAuth "aud" claim and if this value is set, the broker will match the value from JWT's "aud" claim to see if there is an exact match. If there is no match, the broker will reject the JWT and authentication will fail.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.expected.issuer"></a><a id="mirror_connector_sasl.oauthbearer.expected.issuer" href="#mirror_connector_sasl.oauthbearer.expected.issuer">sasl.oauthbearer.expected.issuer</a></h4>
-<p>The (optional) setting for the broker to use to verify that the JWT was created by the expected issuer. The JWT will be inspected for the standard OAuth "iss" claim and if this value is set, the broker will match it exactly against what is in the JWT's "iss" claim. If there is no match, the broker will reject the JWT and authentication will fail.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.header.urlencode"></a><a id="mirror_connector_sasl.oauthbearer.header.urlencode" href="#mirror_connector_sasl.oauthbearer.header.urlencode">sasl.oauthbearer.header.urlencode</a></h4>
-<p>The (optional) setting to enable the OAuth client to URL-encode the client_id and client_secret in the authorization header in accordance with RFC6749, see <a href="https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1">here</a> for more details. The default value is set to 'false' for backward compatibility</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.refresh.ms"></a><a id="mirror_connector_sasl.oauthbearer.jwks.endpoint.refresh.ms" href="#mirror_connector_sasl.oauthbearer.jwks.endpoint.refresh.ms">sasl.oauthbearer.jwks.endpoint.refresh.ms</a></h4>
-<p>The (optional) value in milliseconds for the broker to wait between refreshing its JWKS (JSON Web Key Set) cache that contains the keys to verify the signature of the JWT.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>3600000 (1 hour)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms"></a><a id="mirror_connector_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms" href="#mirror_connector_sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms</a></h4>
-<p>The (optional) value in milliseconds for the maximum wait between attempts to retrieve the JWKS (JSON Web Key Set) from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>10000 (10 seconds)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.jwks.endpoint.retry.backoff.ms"></a><a id="mirror_connector_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms" href="#mirror_connector_sasl.oauthbearer.jwks.endpoint.retry.backoff.ms">sasl.oauthbearer.jwks.endpoint.retry.backoff.ms</a></h4>
-<p>The (optional) value in milliseconds for the initial wait between JWKS (JSON Web Key Set) retrieval attempts from the external authentication provider. JWKS retrieval uses an exponential backoff algorithm with an initial wait based on the sasl.oauthbearer.jwks.endpoint.retry.backoff.ms setting and will double in wait length between attempts up to a maximum wait length specified by the sasl.oauthbearer.jwks.endpoint.retry.backoff.max.ms setting.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.scope.claim.name"></a><a id="mirror_connector_sasl.oauthbearer.scope.claim.name" href="#mirror_connector_sasl.oauthbearer.scope.claim.name">sasl.oauthbearer.scope.claim.name</a></h4>
-<p>The OAuth claim for the scope is often named "scope", but this (optional) setting can provide a different name to use for the scope included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>scope</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sasl.oauthbearer.sub.claim.name"></a><a id="mirror_connector_sasl.oauthbearer.sub.claim.name" href="#mirror_connector_sasl.oauthbearer.sub.claim.name">sasl.oauthbearer.sub.claim.name</a></h4>
-<p>The OAuth claim for the subject is often named "sub", but this (optional) setting can provide a different name to use for the subject included in the JWT payload's claims if the OAuth/OIDC provider uses a different name for that claim.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>sub</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.cipher.suites"></a><a id="mirror_connector_ssl.cipher.suites" href="#mirror_connector_ssl.cipher.suites">ssl.cipher.suites</a></h4>
-<p>A list of cipher suites. This is a named combination of authentication, encryption, MAC and key exchange algorithm used to negotiate the security settings for a network connection using TLS or SSL network protocol. By default all the available cipher suites are supported.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.endpoint.identification.algorithm"></a><a id="mirror_connector_ssl.endpoint.identification.algorithm" href="#mirror_connector_ssl.endpoint.identification.algorithm">ssl.endpoint.identification.algorithm</a></h4>
-<p>The endpoint identification algorithm to validate server hostname using server certificate. </p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>https</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.engine.factory.class"></a><a id="mirror_connector_ssl.engine.factory.class" href="#mirror_connector_ssl.engine.factory.class">ssl.engine.factory.class</a></h4>
-<p>The class of type org.apache.kafka.common.security.auth.SslEngineFactory to provide SSLEngine objects. Default value is org.apache.kafka.common.security.ssl.DefaultSslEngineFactory. Alternatively, setting this to org.apache.kafka.common.security.ssl.CommonNameLoggingSslEngineFactory will log the common name of expired SSL certificates used by clients to authenticate at any of the brokers with log level INFO. Note that this will cause a tiny delay during establishment of new connection [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.keymanager.algorithm"></a><a id="mirror_connector_ssl.keymanager.algorithm" href="#mirror_connector_ssl.keymanager.algorithm">ssl.keymanager.algorithm</a></h4>
-<p>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>SunX509</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.secure.random.implementation"></a><a id="mirror_connector_ssl.secure.random.implementation" href="#mirror_connector_ssl.secure.random.implementation">ssl.secure.random.implementation</a></h4>
-<p>The SecureRandom PRNG implementation to use for SSL cryptography operations. </p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="ssl.trustmanager.algorithm"></a><a id="mirror_connector_ssl.trustmanager.algorithm" href="#mirror_connector_ssl.trustmanager.algorithm">ssl.trustmanager.algorithm</a></h4>
-<p>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>PKIX</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="name"></a><a id="mirror_connector_name" href="#mirror_connector_name">name</a></h4>
-<p>Globally unique name to use for this connector.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td>non-empty string without ISO control characters</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="connector.class"></a><a id="mirror_connector_connector.class" href="#mirror_connector_connector.class">connector.class</a></h4>
-<p>Name or alias of the class for this connector. Must be a subclass of org.apache.kafka.connect.connector.Connector. If the connector is org.apache.kafka.connect.file.FileStreamSinkConnector, you can either specify this full name, or use "FileStreamSink" or "FileStreamSinkConnector" to make the configuration a bit shorter</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td></td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="connector.plugin.version"></a><a id="mirror_connector_connector.plugin.version" href="#mirror_connector_connector.plugin.version">connector.plugin.version</a></h4>
-<p>Version of the connector.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>org.apache.kafka.connect.runtime.ConnectorConfig$PluginVersionValidator@4a87761d</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="tasks.max"></a><a id="mirror_connector_tasks.max" href="#mirror_connector_tasks.max">tasks.max</a></h4>
-<p>Maximum number of tasks to use for this connector.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td>[1,...]</td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="tasks.max.enforce"></a><a id="mirror_connector_tasks.max.enforce" href="#mirror_connector_tasks.max.enforce">tasks.max.enforce</a></h4>
-<p>(Deprecated) Whether to enforce that the tasks.max property is respected by the connector. By default, connectors that generate too many tasks will fail, and existing sets of tasks that exceed the tasks.max property will also be failed. If this property is set to false, then connectors will be allowed to generate more than the maximum number of tasks, and existing sets of tasks that exceed the tasks.max property will be allowed to run. This property is deprecated and will be removed i [...]
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="key.converter"></a><a id="mirror_connector_key.converter" href="#mirror_connector_key.converter">key.converter</a></h4>
-<p>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the keys in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>A concrete subclass of org.apache.kafka.connect.storage.Converter, A class with a public, no-argument constructor</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="key.converter.plugin.version"></a><a id="mirror_connector_key.converter.plugin.version" href="#mirror_connector_key.converter.plugin.version">key.converter.plugin.version</a></h4>
-<p>Version of the key converter.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>org.apache.kafka.connect.runtime.ConnectorConfig$PluginVersionValidator@66d1af89</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="value.converter"></a><a id="mirror_connector_value.converter" href="#mirror_connector_value.converter">value.converter</a></h4>
-<p>Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>A concrete subclass of org.apache.kafka.connect.storage.Converter, A class with a public, no-argument constructor</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="value.converter.plugin.version"></a><a id="mirror_connector_value.converter.plugin.version" href="#mirror_connector_value.converter.plugin.version">value.converter.plugin.version</a></h4>
-<p>Version of the value converter.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>org.apache.kafka.connect.runtime.ConnectorConfig$PluginVersionValidator@8646db9</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="header.converter"></a><a id="mirror_connector_header.converter" href="#mirror_connector_header.converter">header.converter</a></h4>
-<p>HeaderConverter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the header values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro. By default, the SimpleHeaderConverter is used to serialize header values to strings and deserialize them by inferring the sche [...]
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>A concrete subclass of org.apache.kafka.connect.storage.HeaderConverter, A class with a public, no-argument constructor</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="header.converter.plugin.version"></a><a id="mirror_connector_header.converter.plugin.version" href="#mirror_connector_header.converter.plugin.version">header.converter.plugin.version</a></h4>
-<p>Version of the header converter.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>null</td></tr>
-<tr><th>Valid Values:</th><td>org.apache.kafka.connect.runtime.ConnectorConfig$PluginVersionValidator@37374a5e</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="config.action.reload"></a><a id="mirror_connector_config.action.reload" href="#mirror_connector_config.action.reload">config.action.reload</a></h4>
-<p>The action that Connect should take on the connector when changes in external configuration providers result in a change in the connector's configuration properties. A value of 'none' indicates that Connect will do nothing. A value of 'restart' indicates that Connect should restart/reload the connector with the updated configuration properties.The restart may actually be scheduled in the future if the external configuration provider indicates that a configuration value will expire in [...]
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>restart</td></tr>
-<tr><th>Valid Values:</th><td>[none, restart]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="transforms"></a><a id="mirror_connector_transforms" href="#mirror_connector_transforms">transforms</a></h4>
-<p>Aliases for the transformations to be applied to records.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td>non-null string, unique transformation aliases</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="predicates"></a><a id="mirror_connector_predicates" href="#mirror_connector_predicates">predicates</a></h4>
-<p>Aliases for the predicates used by transformations.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>""</td></tr>
-<tr><th>Valid Values:</th><td>non-null string, unique predicate aliases</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="errors.retry.timeout"></a><a id="mirror_connector_errors.retry.timeout" href="#mirror_connector_errors.retry.timeout">errors.retry.timeout</a></h4>
-<p>The maximum duration in milliseconds that a failed operation will be reattempted. The default is 0, which means no retries will be attempted. Use -1 for infinite retries.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>0</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="errors.retry.delay.max.ms"></a><a id="mirror_connector_errors.retry.delay.max.ms" href="#mirror_connector_errors.retry.delay.max.ms">errors.retry.delay.max.ms</a></h4>
-<p>The maximum duration in milliseconds between consecutive retry attempts. Jitter will be added to the delay once this limit is reached to prevent thundering herd issues.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>60000 (1 minute)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="errors.tolerance"></a><a id="mirror_connector_errors.tolerance" href="#mirror_connector_errors.tolerance">errors.tolerance</a></h4>
-<p>Behavior for tolerating errors during connector operation. 'none' is the default value and signals that any error will result in an immediate connector task failure; 'all' changes the behavior to skip over problematic records.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>none</td></tr>
-<tr><th>Valid Values:</th><td>[none, all]</td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="errors.log.enable"></a><a id="mirror_connector_errors.log.enable" href="#mirror_connector_errors.log.enable">errors.log.enable</a></h4>
-<p>If true, write each error and the details of the failed operation and problematic record to the Connect application log. This is 'false' by default, so that only errors that are not tolerated are reported.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="errors.log.include.messages"></a><a id="mirror_connector_errors.log.include.messages" href="#mirror_connector_errors.log.include.messages">errors.log.include.messages</a></h4>
-<p>Whether to include in the log the Connect record that resulted in a failure. For sink records, the topic, partition, offset, and timestamp will be logged. For source records, the key and value (and their schemas), all headers, and the timestamp, Kafka topic, Kafka partition, source partition, and source offset will be logged. This is 'false' by default, which will prevent record keys, values, and headers from being written to log files.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>false</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>medium</td></tr>
-</tbody></table>
-</li>
-</ul>
-
diff --git a/content/en/43/generated/mirror_heartbeat_config.html b/content/en/43/generated/mirror_heartbeat_config.html
index f74447fee3..e69de29bb2 100644
--- a/content/en/43/generated/mirror_heartbeat_config.html
+++ b/content/en/43/generated/mirror_heartbeat_config.html
@@ -1,33 +0,0 @@
-<ul class="config-list">
-<li>
-<h4><a id="emit.heartbeats.enabled"></a><a id="mirror_heartbeat_emit.heartbeats.enabled" href="#mirror_heartbeat_emit.heartbeats.enabled">emit.heartbeats.enabled</a></h4>
-<p>Whether to emit heartbeats to target cluster.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="emit.heartbeats.interval.seconds"></a><a id="mirror_heartbeat_emit.heartbeats.interval.seconds" href="#mirror_heartbeat_emit.heartbeats.interval.seconds">emit.heartbeats.interval.seconds</a></h4>
-<p>Frequency of heartbeats.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>1</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="heartbeats.topic.replication.factor"></a><a id="mirror_heartbeat_heartbeats.topic.replication.factor" href="#mirror_heartbeat_heartbeats.topic.replication.factor">heartbeats.topic.replication.factor</a></h4>
-<p>Replication factor for heartbeats topic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-</ul>
-
diff --git a/content/en/43/generated/mirror_source_config.html b/content/en/43/generated/mirror_source_config.html
index 87c1c6a0f6..e69de29bb2 100644
--- a/content/en/43/generated/mirror_source_config.html
+++ b/content/en/43/generated/mirror_source_config.html
@@ -1,193 +0,0 @@
-<ul class="config-list">
-<li>
-<h4><a id="config.properties.exclude"></a><a id="mirror_source_config.properties.exclude" href="#mirror_source_config.properties.exclude">config.properties.exclude</a></h4>
-<p>Topic config properties that should not be replicated. Supports comma-separated property names and regexes.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>follower.replication.throttled.replicas,leader.replication.throttled.replicas,message.timestamp.difference.max.ms,log.message.timestamp.before.max.ms,log.message.timestamp.after.max.ms,message.timestamp.type,unclean.leader.election.enable,min.insync.replicas</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="topics"></a><a id="mirror_source_topics" href="#mirror_source_topics">topics</a></h4>
-<p>Topics to replicate. Supports comma-separated topic names and regexes.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>.*</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="topics.exclude"></a><a id="mirror_source_topics.exclude" href="#mirror_source_topics.exclude">topics.exclude</a></h4>
-<p>Excluded topics. Supports comma-separated topic names and regexes. Excludes take precedence over includes.</p>
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>mm2.*\.internal,.*\.replica,__.*</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>high</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="config.property.filter.class"></a><a id="mirror_source_config.property.filter.class" href="#mirror_source_config.property.filter.class">config.property.filter.class</a></h4>
-<p>ConfigPropertyFilter to use. Selects topic config properties to replicate.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.connect.mirror.DefaultConfigPropertyFilter</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="consumer.poll.timeout.ms"></a><a id="mirror_source_consumer.poll.timeout.ms" href="#mirror_source_consumer.poll.timeout.ms">consumer.poll.timeout.ms</a></h4>
-<p>Timeout when polling source cluster.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>1000 (1 second)</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="emit.offset-syncs.enabled"></a><a id="mirror_source_emit.offset-syncs.enabled" href="#mirror_source_emit.offset-syncs.enabled">emit.offset-syncs.enabled</a></h4>
-<p>Whether to store the new offset of the replicated records in offset-syncs topic or not. MirrorCheckpointConnector will not be able to sync group offsets or emit checkpoints if emit.checkpoints.enabled and/or sync.group.offsets.enabled are enabled while emit.offset-syncs.enabled is disabled.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="heartbeats.replication.enabled"></a><a id="mirror_source_heartbeats.replication.enabled" href="#mirror_source_heartbeats.replication.enabled">heartbeats.replication.enabled</a></h4>
-<p>Whether to replicate the heartbeats topics even when the topic filter does not include them. If set to true, heartbeats topics identified by the replication policy will always be replicated, regardless of the topic filter configuration. If set to false, heartbeats topics will only be replicated if the topic filter allows.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="metric.names.formats"></a><a id="mirror_source_metric.names.formats" href="#mirror_source_metric.names.formats">metric.names.formats</a></h4>
-<p>Deprecated. The formats in which metrics are emitted. Valid values are legacy and new. When set to legacy, the metrics have the following name "kafka.connect.mirror:type=MirrorSourceConnector,source={SOURCE},target={TARGET},topic={TOPIC},partition={PARTITION}". When set to new, the metrics have the following name "kafka.connect:type=plugins,connector={CONNECTOR},task={TASK},source={SOURCE},target={TARGET},topic={TOPIC},partition={PARTITION}". When set to "legacy,new" the connector wil [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
-<tr><th>Default:</th><td>legacy</td></tr>
-<tr><th>Valid Values:</th><td>[legacy, new]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offset-syncs.topic.location"></a><a id="mirror_source_offset-syncs.topic.location" href="#mirror_source_offset-syncs.topic.location">offset-syncs.topic.location</a></h4>
-<p>The location (source/target) of the offset-syncs topic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>string</td></tr>
-<tr><th>Default:</th><td>source</td></tr>
-<tr><th>Valid Values:</th><td>[source, target]</td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offset-syncs.topic.replication.factor"></a><a id="mirror_source_offset-syncs.topic.replication.factor" href="#mirror_source_offset-syncs.topic.replication.factor">offset-syncs.topic.replication.factor</a></h4>
-<p>Replication factor for offset-syncs topic.</p>
-<table><tbody>
-<tr><th>Type:</th><td>short</td></tr>
-<tr><th>Default:</th><td>3</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="offset.lag.max"></a><a id="mirror_source_offset.lag.max" href="#mirror_source_offset.lag.max">offset.lag.max</a></h4>
-<p>How out-of-sync a remote partition can be before it is resynced.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>100</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="refresh.topics.enabled"></a><a id="mirror_source_refresh.topics.enabled" href="#mirror_source_refresh.topics.enabled">refresh.topics.enabled</a></h4>
-<p>Whether to periodically check for new topics and partitions.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="refresh.topics.interval.seconds"></a><a id="mirror_source_refresh.topics.interval.seconds" href="#mirror_source_refresh.topics.interval.seconds">refresh.topics.interval.seconds</a></h4>
-<p>Frequency of topic refresh.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>600</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="replication.factor"></a><a id="mirror_source_replication.factor" href="#mirror_source_replication.factor">replication.factor</a></h4>
-<p>Replication factor for newly created remote topics.</p>
-<table><tbody>
-<tr><th>Type:</th><td>int</td></tr>
-<tr><th>Default:</th><td>2</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sync.topic.acls.enabled"></a><a id="mirror_source_sync.topic.acls.enabled" href="#mirror_source_sync.topic.acls.enabled">sync.topic.acls.enabled</a></h4>
-<p>Whether to periodically configure remote topic ACLs to match their corresponding upstream topics.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sync.topic.acls.interval.seconds"></a><a id="mirror_source_sync.topic.acls.interval.seconds" href="#mirror_source_sync.topic.acls.interval.seconds">sync.topic.acls.interval.seconds</a></h4>
-<p>Frequency of topic ACL sync.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>600</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sync.topic.configs.enabled"></a><a id="mirror_source_sync.topic.configs.enabled" href="#mirror_source_sync.topic.configs.enabled">sync.topic.configs.enabled</a></h4>
-<p>Whether to periodically configure remote topics to match their corresponding upstream topics.</p>
-<table><tbody>
-<tr><th>Type:</th><td>boolean</td></tr>
-<tr><th>Default:</th><td>true</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="sync.topic.configs.interval.seconds"></a><a id="mirror_source_sync.topic.configs.interval.seconds" href="#mirror_source_sync.topic.configs.interval.seconds">sync.topic.configs.interval.seconds</a></h4>
-<p>Frequency of topic config sync.</p>
-<table><tbody>
-<tr><th>Type:</th><td>long</td></tr>
-<tr><th>Default:</th><td>600</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-<li>
-<h4><a id="topic.filter.class"></a><a id="mirror_source_topic.filter.class" href="#mirror_source_topic.filter.class">topic.filter.class</a></h4>
-<p>TopicFilter to use. Selects topics to replicate.</p>
-<table><tbody>
-<tr><th>Type:</th><td>class</td></tr>
-<tr><th>Default:</th><td>org.apache.kafka.connect.mirror.DefaultTopicFilter</td></tr>
-<tr><th>Valid Values:</th><td></td></tr>
-<tr><th>Importance:</th><td>low</td></tr>
-</tbody></table>
-</li>
-</ul>
-
diff --git a/content/en/43/generated/producer_config.html b/content/en/43/generated/producer_config.html
index 14c84724a1..e69de29bb2 100644
--- a/content/en/43/generated/producer_config.html
+++ b/content/en/43/generated/producer_config.html
@@ -1,1133 +0,0 @@
-<ul class="config-list">
-<li>
-<h4><a id="bootstrap.servers"></a><a id="producerconfigs_bootstrap.servers" href="#producerconfigs_bootstrap.servers">bootstrap.servers</a></h4>
-<p>A list of host/port pairs used to establish the initial connection to the Kafka cluster. Clients use this list to bootstrap and discover the full set of Kafka brokers. While the order of servers in the list does not matter, we recommend including more than one server to ensure resilience if any servers are down. This list does not need to contain the entire set of brokers, as Kafka clients automatically manage and update connections to the cluster efficiently. This list must be in the [...]
-<table><tbody>
-<tr><th>Type:</th><td>list</td></tr>
... 23349 lines suppressed ...