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.

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

Tagging the ClientUpgradeRequest to be able to support per-reqiest client ssl auth #12660

Open
iiliev2 opened this issue Dec 20, 2024 · 0 comments

Comments

@iiliev2
Copy link

iiliev2 commented Dec 20, 2024

Jetty 12

In relation to #12659

The proxy uses secured transports, similar to the examples in org.eclipse.jetty.proxy.ClientAuthProxyTest

A websocket proxy must also be able to tag the ClientUpgradeRequest in order to be able to setup the ssl handshaking process to select a specific certificate on a per-request basis.

ClientUpgradeRequest upgradeRequest = ...
upgradeRequest.tag(new AliasTLSTag(...));
webClient.connect(endpoint, upgradeRequest, null);

Currently there is no way to do this with the websocket client AFAICT, but the underlying core client should be able to to it. So it is a matter of exposing such a method and copying the tag over to JettyClientUpgradeRequest in the connect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant