apache / apache/pulsar

Websocket decrypting the message support

Open
#11,197 2 comments 0 reactions 0 assignees View on GitHub
lifecycle/stale type/enhancement
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

Hi Right now
websocket allows the encrypted payload to be passed thru to the client.

Can we get the fields how client is using to manage decryption and also update in the websocket document
https://pulsar.apache.org/docs/en/client-libraries-websocket/#consumer-endpoint
as of know this are the fields
![image](https://user-images.githubusercontent.com/59704044/124283659-c6225d80-db11-11eb-8bf2-57b52e66afb3.png)

and the above mentioned "key" ("Original routing key set by producer") is actually the '(aes) encrypted data key' ?

https://github.com/apache/pulsar/issues/10021

Contributor guide

Open the contributing guide

Research direction

Start with the Consumer Endpoint section in the Pulsar WebSocket documentation and compare its listed fields with the decryption fields shown in the issue. Read the related issue #10021 to understand the existing discussion. Done means the WebSocket behavior and client-facing decryption fields are resolved and the documentation accurately describes them.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, documentation, security
Issue type
Feature
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.