apache / apache/pulsar-client-node

Authenticating using a Token

未关闭
#99 11 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
triage/week-27 type/question
主要语言
C++
星标
164
派生
98
PR 合并指标
30 天内没有已合并 PR

描述

Hi,

I am trying to use a token to create a producer but keep getting the following message
```
INFO ClientConnection:330 | [ -> ] Connected to broker
ERROR ClientConnection:388 | [ -> ] Handshake failed: certificate verify failed
INFO ClientConnection:1349 | [ -> ] Connection closed
ERROR ClientImpl:182 | Error Checking/Getting Partition Metadata while creating producer on persistent://[topic] -- 5
```

When I try to connect locally using a token, it seems to work however when I am running it in production, I am seeing the above messages. Therefore, not sure how to replicate it locally.

Is there a way to use the token or do I have to use the certification / private key approach when initializing the client:
`return new pulsar.Client({ ..., auth: { certificatePath: '', privateKeyPath: '' })

贡献指南

这个仓库没有索引到贡献指南

调研方向

The report names no repository file or test. Start by comparing the local and production client initialization, focusing on the token setup and the certificatePath/privateKeyPath alternative, then trace the reported certificate verification failure. Done means establishing whether token authentication can create a producer in production without the handshake error.

由索引模型根据 Issue 内容生成。

评估

技术栈
javascript, nodejs
领域
authentication
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。