Support for custom keystore for secure websocket api.

[skoya]

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

[skoya]

hi, how do we get this prioritized?

[arash009]

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