apache / apache/pulsar-client-node

Authenticating using a Token

Ouverte
#99 11 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
triage/week-27 type/question
Langage dominant
C++
Étoiles
164
Forks
98
Métriques de merge des PR
Aucune PR mergée en 30 j

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

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
javascript, nodejs
Domaine
authentication
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.