TLS client certificate and key configuration in built-in fetch (2-way TLS) #79653
Unanswered
alinayebi9080
asked this question in
Help
Replies: 1 comment
-
Great point — this is currently a known limitation with 🤔 Why doesn’t it work?The built-in ✅ Workaround (until native support)Use Node.js's Option 1:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
The built-in
fetch
provided by Next.js (when used in server components or API routes) currently lacks support for configuring client TLS options, such ascert
,key
, andca
for mutual TLS (2-way TLS) authentication.This limitation prevents secure communication with external services that require 2-way TLS, which is common in enterprise APIs or private services.
I'd like the ability to pass custom HTTPS agent options to
fetch
, such as:Beta Was this translation helpful? Give feedback.
All reactions