[GH-ISSUE #465] Missing Authority Key Identifier in Server Certificate #464

New issue

Open

opened 2026-03-03 19:50:44 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 19:50:44 +03:00

Owner

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

Originally assigned to: @kics223w1 on GitHub.

Description

Original ticket: https://github.com/ProxymanApp/Proxyman/issues/2226

How to reproduce

Open Proxyman Windows on Mac -> Intercept producthunt.com
Open Google Chrome -> Visit producthunt.com -> Click on the Setting -> Export the certificate to the Desktop file
Use the Preview app to preview it
No Authority Key Identifier in the certificate, which is issued by Proxyman CA

Acceptance Criteria

Preview ca.js file and ServerExtensions and find a solution to add Authority Key Identifier with value: keyid:always,issuer
Test it:

Do Factory Reset first to make sure all cached certificated are deleted -> Install new Proxyman CA Certificate in Keychains
Perform the How to reproduce to export the cert
Verify There is an Authority Key Identifier in the cert ✅

Verify that this value (Authority Key Identifier) is the same as with the Proxyman Root CA's Subject Key Identifier in Keychain (Open System Keychain -> SEarch Proxyman CA -> Preview it -> Verify)

Verify that Windows works fine. Try intercept all domains, verify we can see HTTPS data as usual

Originally created by @NghiaTranUIT on GitHub (Jan 5, 2025). Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/465 Originally assigned to: @kics223w1 on GitHub. ## Description - Original ticket: https://github.com/ProxymanApp/Proxyman/issues/2226 ## How to reproduce 1. Open Proxyman Windows on Mac -> Intercept producthunt.com 2. Open Google Chrome -> Visit producthunt.com -> Click on the Setting -> Export the certificate to the Desktop file <img width="492" alt="Screenshot 2025-01-05 at 10 38 10 AM" src="https://github.com/user-attachments/assets/6a52bdb9-f839-41aa-a7ca-663baae323ec" /> 3. Use the Preview app to preview it 4. No `Authority Key Identifier` in the certificate, which is issued by Proxyman CA ![Screenshot 2025-01-05 at 10 36 29 AM](https://github.com/user-attachments/assets/e227396c-333c-4bfb-8a88-66f4158cb4db) ## Acceptance Criteria - [x] Preview `ca.js` file and `ServerExtensions` and find a solution to add `Authority Key Identifier` with value: `keyid:always,issuer` - [ ] Test it: 1. Do `Factory Reset` first to make sure all cached certificated are deleted -> Install new Proxyman CA Certificate in Keychains 2. Perform the `How to reproduce` to export the cert 3. Verify There is an Authority Key Identifier in the cert ✅ ![Screenshot 2025-01-05 at 10 35 17 AM](https://github.com/user-attachments/assets/584a7349-032d-4907-a348-b565aaa18104) 4. Verify that this value (Authority Key Identifier) is the same as with the Proxyman Root CA's Subject Key Identifier in Keychain (Open System Keychain -> SEarch Proxyman CA -> Preview it -> Verify) ![Screenshot 2025-01-05 at 10 50 09 AM](https://github.com/user-attachments/assets/993a8904-3252-4906-a456-5e28dfd6f652) - [ ] Verify that Windows works fine. Try intercept all domains, verify we can see HTTPS data as usual