卡夫卡：listener.name.internal.ssl.endpoint.identification.algorithm 对比 ssl.endpoint.identification.algorithm
Kafka: listener.name.internal.ssl.endpoint.identification.algorithm vs ssl.endpoint.identification.algorithm
我在网上搜索过，但我无法理解这两个 Kafka 属性之间的区别：
- listener.name.internal.ssl.endpoint.identification.algorithm
- ssl.endpoint.identification.algorithm
它们一样吗？
listener.name.internal.* 属性仅在您将 INTERNAL:// 作为 listeners 配置时适用，并且您想要覆盖默认值。
否则所有听众都会使用ssl.endpoint.identification.algorithm
来自文档
Different security (SSL and SASL) settings can be configured for each listener by adding a normalised prefix (the listener name is lowercased) to the config name. For example, to set a different keystore for the INTERNAL listener, a config with name listener.name.internal.ssl.keystore.location would be set. If the config for the listener name is not set, the config will fallback to the generic config (i.e. ssl.keystore.location)
我在网上搜索过，但我无法理解这两个 Kafka 属性之间的区别：
- listener.name.internal.ssl.endpoint.identification.algorithm
- ssl.endpoint.identification.algorithm
它们一样吗？
listener.name.internal.* 属性仅在您将 INTERNAL:// 作为 listeners 配置时适用，并且您想要覆盖默认值。
否则所有听众都会使用ssl.endpoint.identification.algorithm
来自文档
Different security (SSL and SASL) settings can be configured for each listener by adding a normalised prefix (the listener name is lowercased) to the config name. For example, to set a different keystore for the
INTERNALlistener, a config with namelistener.name.internal.ssl.keystore.locationwould be set. If the config for the listener name is not set, the config will fallback to the generic config (i.e.ssl.keystore.location)