Interesting request. Currently there is no support for that. Wonder where a good place for that would be ...
Gut reaction is to make it available via the WebSocketCreator, letting you capture and hold onto it at websocket creation time. That would make it server side specific functionality, which is what i think you intend. Another option would be to expose the SSL details via the Session object, but what that would mean to the websocket-client implementation of Session I don't know (yet) -- Joakim Erdfelt <[email protected]> webtide.com <http://www.webtide.com/> Developer advice, services and support from the Jetty & CometD experts eclipse.org/jetty - cometd.org On Sun, Jun 9, 2013 at 8:40 AM, Erich Bremer <[email protected]> wrote: > Hi, > > I have a case where I am encrypting a websockets connection and > requiring a client give it's certificate during the initial http connection > before upgrading to a encrypted WebSockets connection. What is the easiest > way to get hold of the client certificate for a particular websockets > connection? I've only been able to do this by modifying the core Jetty > code by passing the certificate to the websocket pojo in a modified > websocketfactory. I'm hoping there is an easier way, thanks! - Erich > ______________________________**_________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/**mailman/listinfo/jetty-users<https://dev.eclipse.org/mailman/listinfo/jetty-users> >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
