ChatGPTNextWeb/NextChat

[Feature] configurable **client** certificate

Open

#3,935 opened on Jan 27, 2024

View on GitHub
 (3 comments) (0 reactions) (0 assignees)TypeScript (59,717 forks)batch import
backloghelp wanted

Repository metrics

Stars
 (87,992 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hi, I encountered a problem with the client certificate verifying / authenticating.

When enabled client certs (typically the Cloudflare mTLS rules), the client must present its private cert (aka .p12/.pfx file) to the server. However since ChatGPT-Next-Web requests the API base from the backend, it would not carry the valid credentials that should have come from a browser request.

So there should be a configurable option to specify a client certificate so that the mutual verification would work.

I have read the issue list and found that #518 #3034 may be related, but both of them didn't mention if it's possible to deploy a client certificate for the backend.

My current approach is to allow the server IP as request src_ip, but it's quite inconvenient since I had to hard code the IP into the rules. So let me ask for a feature to satisfy this scene.

Contributor guide

Research direction
Investigate how to add client certificate configuration to the backend proxy. Look at the existing API base request handling and modify it to support HTTPS agent with client cert and key from environment variables or config file.
Tech stack
typescriptnodejs
Domain
backendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitmTLS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40