[
https://issues.apache.org/jira/browse/KAFKA-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659824#comment-16659824
]
Sophie Qian edited comment on KAFKA-7530 at 10/22/18 11:41 PM:
---------------------------------------------------------------
Our problem is with runnning Confluent Schema Registry in docker container.
I got following warning msg after export
{color:#14892c}SCHEMA_REGISTRY_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM_CONFIG=""
{color}
{color:#d04437}[2018-10-22 17:58:10,058] WARN The configuration
'ssl.endpoint.identification.algorithm.config' was supplied but isn't a known
config. (org.apache.kafka.clients.admin.AdminClientConfig){color}
{color:#d04437}{color:#333333}The value for
ssl.endpoint.identification.algorithm.config in
/etc/schema-registry/schema-registry.properties is not been taken into
consideration. it's empty string in the properties file{color}
{color:#14892c}(
{color}{color}{color:#14892c}ssl.endpoint.identification.algorithm.config=
){color}
Schema registry log showing ssl.endpoint.identification.algorithm is using
"https"
[2018-10-22 23:26:43,039] INFO AdminClientConfig values:
..
ssl.enabled.protocols = [TLSv1.2, TLSv1.1, TLSv1]
{color:#d04437}ssl.endpoint.identification.algorithm = https{color}
....
{color:#d04437} {color}
was (Author: kafka):
Our problem is with runnning Confluent Schema Registry in docker container.
I got following warning msg after export
{color:#14892c}SCHEMA_REGISTRY_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM_CONFIG=""
{color}
{color:#d04437}[2018-10-22 17:58:10,058] WARN The configuration
'ssl.endpoint.identification.algorithm.config' was supplied but isn't a known
config. (org.apache.kafka.clients.admin.AdminClientConfig){color}
{color:#d04437}{color:#333333}The value for
ssl.endpoint.identification.algorithm.config in
/etc/schema-registry/schema-registry.properties is not been taken into
consideration. it's empty string in the properties file (
{color}{color}{color:#14892c}ssl.endpoint.identification.algorithm.config={color}
)
Schema registry log showing ssl.endpoint.identification.algorithm is using
"https"
[2018-10-22 23:26:43,039] INFO AdminClientConfig values:
..
ssl.enabled.protocols = [TLSv1.2, TLSv1.1, TLSv1]
{color:#d04437}ssl.endpoint.identification.algorithm = https{color}
....
{color:#d04437} {color}
> Need to allow overwrite ssl.endpoint.identification.algorithm.config
> --------------------------------------------------------------------
>
> Key: KAFKA-7530
> URL: https://issues.apache.org/jira/browse/KAFKA-7530
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 2.0.0
> Reporter: Sophie Qian
> Priority: Major
>
> We are in the process of upgrading our system to use Confluent 5.0.0 (which
> is using Kafka 2.0.0). I found out SslConfigs (
> clients/src/main/java/org/apache/kafka/common/config/SslConfigs.java) has
> following change:
>
> {color:#14892c}KAFKA-3665: Enable TLS hostname verification by default
> (KIP-294) (#4956){color}
> {color:#14892c}Make HTTPS the default
> ssl.endpoint.identification.algorithm.{color}
>
> But user can not overwrite ssl.endpoint.identification.alogorithm, only
> following values can be reconfigurable.
> {color:#205081}public static final Set<String> RECONFIGURABLE_CONFIGS =
> Utils.mkSet(
> ¦ SslConfigs.SSL_KEYSTORE_TYPE_CONFIG,
> ¦ SslConfigs.SSL_KEYSTORE_LOCATION_CONFIG,
> ¦ SslConfigs.SSL_KEYSTORE_PASSWORD_CONFIG,
> ¦ SslConfigs.SSL_KEY_PASSWORD_CONFIG,
> ¦ SslConfigs.SSL_TRUSTSTORE_TYPE_CONFIG,
> ¦ SslConfigs.SSL_TRUSTSTORE_LOCATION_CONFIG,
> ¦ SslConfigs.SSL_TRUSTSTORE_PASSWORD_CONFIG);{color}
>
> Pls make SslConfigs.SSL_ENDPOINT_IDENTIFICATION_ALGORITHM_CONFIG
> reconfigurable.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
