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

Client auth configuration parity between rpc-ws and rpc-http #7911

Closed
shorsher opened this issue Nov 22, 2024 · 1 comment
Closed

Client auth configuration parity between rpc-ws and rpc-http #7911

shorsher opened this issue Nov 22, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@shorsher
Copy link
Member

shorsher commented Nov 22, 2024 •
edited
Loading

Description

Currently RPC HTTP TLS client auth can only be configured via a known clients file, however WS SSL client auth can be configured with a trust store. It would be useful to have configuration option parity between the two modes. This way, besu node runners can have a single mechanism for configuring client auth for both HTTP and websockets.

Acceptance Criteria

  • RPC TLS client auth can be configured with a trust store
  • WS TLS client auth can be configured with a known clients file
  • Existing trust options are not impacted
@macfarla macfarla added the enhancement New feature or request label Nov 25, 2024
@macfarla
Copy link
Contributor

macfarla commented Feb 7, 2025

fixed by #7970

@macfarla macfarla closed this as completed Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@macfarla @shorsher