不支持Camel-Kafka安全协议SASL_PLAINTEXT [英] Camel-Kafka security protocol SASL_PLAINTEXT not supported

查看:368
本文介绍了不支持Camel-Kafka安全协议SASL_PLAINTEXT的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我需要使用Camel使用身份验证协议Kerberos将ActiveMQ消息路由到Kafka(Cloudera).

I need to route ActiveMQ messages to Kafka(Cloudera) using Camel using authentication protocol Kerberos.

  • ActiveMQ v5.15.4
  • 骆驼:2.21.1
  • Kafka客户:1.1.0
  • 服务器版本:Apache/2.4.6(CentOS)

Kafka安全性文档指出,它仅支持 SASL_PLAINTEXT
SASL_SSL (用于Kerberos)

Kafka Security documentation states that it only supports SASL_PLAINTEXT and
SASL_SSL for Kerberos

另一方面,当我尝试将 SASL_PLAINTEXT 用于Camel中的安全协议时,在ActiveMQ启动过程中出现错误.结果ActiveMQ将无法启动.

On the other hand when I try to use SASL_PLAINTEXT for security protocol in Camel I am getting an error during the ActiveMQ starting. As a result ActiveMQ will not start.

我从以下网址获取了最新的Camel代码: https://github.com/apache/camel.git ,并指出它仅支持 SSL PLAINTEXT 作为安全协议值.

I took the latest Camel code from: https://github.com/apache/camel.git and it states that it only supports SSL and PLAINTEXT as security protocols values.

我确实找到了已解决的问题: https://access.redhat.com/solutions/3364871 ,但是我没有找到任何证据表明它可以在最新的Camel版本中使用.

I did find this solved issue: https://access.redhat.com/solutions/3364871 but I did not find any evidence that this is working in the latest Camel version.

我的骆驼设置片段是:

<log message="Started The Producer Route" />
<to uri="kafka://10.100.70.00:9092?topic=MyEvents.s1.v1&amp;brokers=10.100.70.00:9092&amp;requestTimeoutMs=305000&amp;retries=3&amp;keySerializerClass=org.apache.kafka.common.serialization.ByteArraySerializer&amp;saslMechanism=GSSAPI&amp;serializerClass=org.apache.kafka.common.serialization.ByteArraySerializer&amp;securityProtocol=SASL_PLAINTEXT&amp;saslKerberosServiceName=kafka"/>

我正在使用外部Jaas配置文件.

I am using an external Jaas configuration file.

骆驼不支持 SASL_PLAINTEXT 吗?

推荐答案

Camel支持 SASL_PLAINTEXT ,因为它使用的是Kafka客户端v1.1.0.问题是实际的安全参数没有传播到Camel界面.这意味着在ActiveMQ启动期间无法识别该参数. 我为此问题打开了问题.

Camel supports SASL_PLAINTEXT as it uses Kafka client v1.1.0. The problem is that the actual security parameter is not propagated to the Camel interface. That means the parameter is not recognised during ActiveMQ startup. I've opened issue for this problem.

这篇关于不支持Camel-Kafka安全协议SASL_PLAINTEXT的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆