forked from whatwg/fetch
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Mutual TLS (mTLS) #3
Comments
I think this extends past just mTLS, to also custom ca certs, and disabling HTTPS verification altogether. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Proposal
I would like to propose that the CG pursue standardization of Mutual TLS authentication in the
fetch
API.This is a feature that is not likely to be implemented by browser runtimes but is in my opinion missing in non-browser runtimes where
fetch
is the only interoperable HTTP client.The use-case I have in mind is implementation of OAuth mTLS Client Authentication and Client Certificate-Bound Access Tokens.
Prior Art
Node.js -
https
module has the option to provide thecert
,key
,crl
,passphrase
,pfx
, andca
options.Deno - using
deno --unstable
there'sDeno.createHttpClient
, the result of which can be passed as aclient
property tofetch
'sinit
argument. This method acceptscertChain
,privateKey
, andcaCerts
options.The text was updated successfully, but these errors were encountered: