[GH-ISSUE #524] Client Certificate #522

Open
opened 2026-03-03 19:51:06 +03:00 by kerem · 0 comments
Owner

Originally created by @NghiaTranUIT on GitHub (Jul 30, 2025).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/524

Originally assigned to: @kics223w1 on GitHub.

Description

Similar to https://github.com/ProxymanApp/proxyman-windows-linux/issues/507, we should implement the Client Certificate

How Client Certificate works?

  • Diagram: Client app -> Proxyman -> Real Server
  • When a Custom Client Certificate is provided by the user, Proxyman will use this Certificate when making an HTTPS connection from [Proxyman -> Real Server]. Make sure [Client app -> Proxyman] side is using the original logic.
  • Custom Client Certificate only affects on [Proxyman -> Real Server]

Criteria

  • Similar to #507 , we should have a service to manage the client certificate and a class to represent the cllient certificate and store it in the user data folder with subfolder: client-certificates

  • Support import via P12 or Pem/Der and passphare (similar to #507 )

  • Client Certificate is using on this side: [Proxyman -> Real Server] and works with

  • HTTPS

  • WSS

  • If the current connection's Host & Port is matched with Custom Client Certificate -> use it

  • Support 0 is a wildcard
    Image

  • Write Unit Tests

Originally created by @NghiaTranUIT on GitHub (Jul 30, 2025). Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/524 Originally assigned to: @kics223w1 on GitHub. ## Description Similar to https://github.com/ProxymanApp/proxyman-windows-linux/issues/507, we should implement the Client Certificate <!-- Failed to upload "Screenshot 2025-07-30 at 20.10.57.jpg" --> ## How Client Certificate works? - Diagram: Client app -> Proxyman -> Real Server - When a Custom Client Certificate is provided by the user, Proxyman will use this Certificate when making an HTTPS connection from [Proxyman -> Real Server]. Make sure [Client app -> Proxyman] side is using the original logic. - Custom Client Certificate only affects on [Proxyman -> Real Server] ### Criteria - [x] Similar to #507 , we should have a service to manage the client certificate and a class to represent the cllient certificate and store it in the user data folder with subfolder: client-certificates - [x] Support import via P12 or Pem/Der and passphare (similar to #507 ) - [x] Client Certificate is using on this side: [Proxyman -> Real Server] and works with - [x] HTTPS - [x] WSS - [x] If the current connection's Host & Port is matched with Custom Client Certificate -> use it - [x] Support 0 is a wildcard <img width="554" height="351" alt="Image" src="https://github.com/user-attachments/assets/7e0bc1c1-bf2d-4150-b454-f86c0abc36dd" /> - [x] Write Unit Tests
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/proxyman-windows-linux#522
No description provided.