You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "poorbarcode (via GitHub)" <gi...@apache.org> on 2023/08/30 05:54:43 UTC
[GitHub] [pulsar] poorbarcode opened a new issue, #21092: [Doc] PIP-290 Provide a way to implement WSS E2E encryption and not need to expose the private key to the WebSocket Proxy
poorbarcode opened a new issue, #21092:
URL: https://github.com/apache/pulsar/issues/21092
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### What issue do you find in Pulsar docs?
After [PIP-290](https://github.com/apache/pulsar/pull/20923), "Provide a way to implement WSS E2E encryption and not need to expose the private key to the WebSocket Proxy", the doc has not been added yet.
### What is your suggestion?
Add the doc for [PIP-290](https://github.com/apache/pulsar/pull/20923)
### Any reference?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
--
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 to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] poorbarcode closed issue #21092: [Doc] PIP-290 Provide a way to implement WSS E2E encryption and not need to expose the private key to the WebSocket Proxy
Posted by "poorbarcode (via GitHub)" <gi...@apache.org>.
poorbarcode closed issue #21092: [Doc] PIP-290 Provide a way to implement WSS E2E encryption and not need to expose the private key to the WebSocket Proxy
URL: https://github.com/apache/pulsar/issues/21092
--
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 to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org