kjaggann commented on issue #10021:
URL: https://github.com/apache/pulsar/issues/10021#issuecomment-873078998
https://github.com/apache/pulsar/issues/11197
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
kjaggann commented on issue #10021:
URL: https://github.com/apache/pulsar/issues/10021#issuecomment-867663749
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-e
kjaggann commented on issue #10021:
URL: https://github.com/apache/pulsar/issues/10021#issuecomment-865108954
The recent change to the pulsar websocket allows the encrypted payload to be
passed thru to the client.
However, it does not appear that the (aes) encrypted data key is included
kjaggann commented on issue #10021:
URL: https://github.com/apache/pulsar/issues/10021#issuecomment-865108954
The recent change to the pulsar websocket allows the encrypted payload to be
passed thru to the client.
However, it does not appear that the (aes) encrypted data key is included
kjaggann commented on issue #10021:
URL: https://github.com/apache/pulsar/issues/10021#issuecomment-844133130
Is this change is in pulsar 2.7.1 version.
however we have upgraded the websocket version in our websocket proxies but
still the user is unable to connect the when the encryption
