-
Notifications
You must be signed in to change notification settings - Fork 104
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
Allow Connecting with a Client Certificate #33
Comments
WebSockex isn't actually able to do that... yet. I've been wanting to look at reworking the If you want to look at patching for yourself in the interim, take a look at where the ssl options are current being set. The options for the Erlang If you need to debug, then it would probably be easier to get a regular |
@Azolo i did need handling for client certificates as well and just gave it a first try, the patch is rather small (about ten lines) and would allow passing Would you be open to a PR for this? do you have anything else in mind - or probably already working elsewhere? |
what i hand in mind - because you already mentioned that ssl options are hard to get right - is that i'd pass that responsibility to the client (=user). define a basic set of options that are normally needed for working web sockets + the ability to pass in everything that's needed in addition to that. that way we keep the library small and focused but still go for flexibility |
@steffkes Indeed |
Hi,
I need to connect with Elixir to a remote Websocket using the client certificate. Would it be possible to put something about this into the documentation. How and where do you specify where is the TLS certificate that you would use at connection establishment?
I looked but can't really find anything on this in the docs.
Many thanks,
Tomaz
The text was updated successfully, but these errors were encountered: