Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support for custom keystore for secure websocket api. #1165

Open
skoya opened this issue Jun 29, 2020 · 2 comments · May be fixed by #7854
Open

Support for custom keystore for secure websocket api. #1165

skoya opened this issue Jun 29, 2020 · 2 comments · May be fixed by #7854
Labels
good first issue Good for newcomers icebox items that need more consideration, time, or can wait

Comments

@skoya
Copy link

skoya commented Jun 29, 2020

Description

As an implementer of Besu, I want enable secure websockets rpc api in the same way TLS is enabled for http so that we can securely call the api with privacy and listen for events.

Acceptance Criteria

  • Expose command line parameters for enabling WS api
  • Expose command line parameters for keystore
  • Expose command line parameters for keystore password file
  • Expose command line parameters for authentication keystore.

Steps to Reproduce (Bug)

  1. attempt to enable TLS for the web socket interface.

Expected behavior:
Expect wss connections from web3j / web3 clients to work.

Actual behavior:
Can enable TLS / Encryption for http but can't for websocket.

Frequency:
n/a

Versions (Add all that apply)

  • Software version: 1.5.0
  • Java version: 11
  • OS Name & Version: any
  • Kernel Version: any
  • Virtual Machine software & version: any
  • Docker Version: any
  • Cloud VM, type, size: any

Additional Information
@rain-on rain-on added the TeamGroot GH issues worked on by Groot Team label Jun 30, 2020
@skoya
Copy link
Author

skoya commented Jul 16, 2020

hi, how do we get this prioritized?

@arash009
Copy link
Contributor

Thank you for suggesting this feature. We’ve added it to our backlog but likely won’t be working on it in the near term.
We’ll reach out if and when we decide to implement this, but if you have any questions in the meantime, or would like help from the Besu community to get a PR started, you can reach out here

@jframe jframe added good first issue Good for newcomers and removed signing labels Nov 1, 2021
@lucassaldanha lucassaldanha added TeamRevenant GH issues worked on by Revenant Team and removed TeamGroot GH issues worked on by Groot Team labels Nov 1, 2021
@non-fungible-nelson non-fungible-nelson added the icebox items that need more consideration, time, or can wait label Mar 6, 2023
@macfarla macfarla removed the TeamRevenant GH issues worked on by Revenant Team label Jul 22, 2024
@pullurib pullurib linked a pull request Nov 4, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers icebox items that need more consideration, time, or can wait
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add TLS/mTLS options for websockets pullurib/besu
8 participants
@skoya @jframe @lucassaldanha @macfarla @vmichalik @arash009 @rain-on @non-fungible-nelson