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

Support client certificate authentication #7

Closed
danopia opened this issue Aug 25, 2021 · 2 comments
Closed

Support client certificate authentication #7

danopia opened this issue Aug 25, 2021 · 2 comments
Labels
enhancement New feature or request upstream Waiting for Deno

Comments

@danopia
Copy link
Member

danopia commented Aug 25, 2021

mTLS support for fetch() just merged into deno's development branch from denoland/deno#11721

Once that merge commit denoland/deno@dccf4cb is in a tagged release we can introduce client certificate support as seen in #5.

Unfortunately, there's still not a way of passing these configurations to a WebSocket client, which continues to keep exec/attach/portforward just a tad out of reach.

@justinmchase
Copy link

Hopefully they will decide to add the options parameter to the websocket like nodejs did, regardless of what the standards group says about it.

@danopia
Copy link
Member Author

danopia commented Aug 29, 2021

I just released v0.3.0 including this. Right now a recent Deno canary build is required. I believe Deno v1.14.0 will be the first proper release with it. In any case --unstable is required.

I'm tracking Deno support for TLS auth in WebSocketStream here: denoland/deno#11846

This library still doesn't have merged WebSocket code so no harm yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request upstream Waiting for Deno
Projects
None yet
Development

No branches or pull requests

2 participants