apache / apache/pulsar-client-node

Authenticating using a Token

Open
#99 11 comments 0 reactions 0 assignees View on GitHub
triage/week-27 type/question
Dominant language
C++
Stars
164
Forks
98
PR merge metrics
No merged PRs in 30d

Description

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: '' })

Contributor guide

No contributing guide indexed for this repository

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.