Allow Wildcards in Client Certificate Host and Port

[karanlyons]

Description

Allow the “Custom Certificates” > “Client Certificates” entries to use wildcards for matching as opposed to explicitly defined Hosts and Ports.

Why this feature/change is important?

Applications will make connections to many different IPs, FQDNs, and ports, all asking for the same client certificate. It is extremely tedious to have to wait for a new connection to appear and fail, go manually add an explicit entry for that connection alone, then retry the connection. And one is likely to miss things while collecting traffic passively. Other proxies do not have this artificial limitation.

[NghiaTranUIT]

May I ask if you want to use wildcard for subdomains, such as *.api.com or domains like *.com ?

[karanlyons]

Ideally there’d be no limitation, and this would operate somewhat like pattern globbing. I’d like to be able to put just * and * down for host and port, or *.example.com or shared-subdomain.* or *.net or 10.0.*.*, etc.

While it appears I can set * for the host this doesn’t actually seem to result in the client cert being offered to any server that asks for one.

[NghiaTranUIT]

thanks, I will implement and sent you a Beta build 👍

[karanlyons]

Wow, thanks! Appreciate the quick turnaround on a feature request :)

[NghiaTranUIT]

@karanlyons let's try this Beta build: https://download.proxyman.io/beta/Proxyman_5.7.0_Support_wildcard_for_host_and_port_in_Custom_Client_Certs.dmg

• It nows allows you to use Wildcard on the Host
• For the Port, use 0 to accept all ports, similar as *

Screenshots