-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
http2 - cannot use client certificate and key #15405
Comments
Definitely. It should be simple to add, tagging as good-first-contribution. |
@mcollina I've been really wanting to make some contributions to the project. I would love to give this a shot if I could get some pointers for getting started. I've been reading through the |
@darahayes yes, definitely! |
@mcollina am I missing something here? I thought this was taken care of by the underlying TLS module. I'm able to use |
@apapirovski I tend to agree (https://github.com/nodejs/node/blob/master/lib/internal/http2/core.js#L2434). However we don't have a test to cover this behavior, so we should probably add that test and updates the docs. |
I did some investigation into this issue and on a separate note I found that currently I had to reinstall my OS over the weekend so I will need to do some more work to reproduce but basically the connection is never fully established for some reason. The debug logs showed @mcollina Should I investigate this and open a proper issue? |
@darahayes open a PR with the fix and unit tests. |
I am merely a noob that happens to be at node.js interactive, but looking at the documentation here it does mention that any options supported by tls.createServer are available. One thing I noticed is that the 'ca' option is passed on tls.connect (via createSecureContext) and not createServer. If you omit this option, a self-signed cert will not work. |
is this still open? would love to give it a shot if someone could guide me a little with where to look and what I need to accomplish :) |
I think @davidmarkclements is working on it. |
PR-URL: nodejs/node#16576 Fixes: nodejs/node#15405 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs/node#16576 Fixes: nodejs/node#15405 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs/node#16576 Fixes: nodejs/node#15405 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Version: 8.4.0
Currently, as a client, you cannot specify a certificate-key pair for authentication. I know that the http2 module is still experimental, but this seems like a useful feature.
The text was updated successfully, but these errors were encountered: