Wildcard Certificate Validation Limits for Multi‑Level Subdomains in Visual Studio
0 reputation · 19 Apr 2023, 05:29 UTC
Wildcard Certificate Validation Limits for Multi‑Level Subdomains in Visual Studio
The goal is to allow Visual Studio to establish TLS connections to services whose hostname contains more than one subdomain level beyond a wildcard certificate (for example, foo.bar.example.com when the certificate is issued to *.example.com).
Current behavior depends on the .NET runtime version bundled with the IDE; some versions enforce a strict single‑subdomain rule and cause the certificate validation to fail, while Visual Studio provides no exposed option to adjust this validation policy.
It remains unclear which specific .NET versions produce the failure, whether newer Visual Studio releases have changed the underlying rule, and what configuration—if any—can be used to permit multi‑level subdomain hostnames without modifying system trust stores.
- Which .NET versions bundled with Visual Studio 2022 enforce the single‑subdomain limit for wildcard certificates?
- Does Visual Studio 2022 version 17.8 or later expose a setting to relax the wildcard validation rule?
- What is the recommended approach to permit connections to hostnames like foo.bar.example.com when using a *.example.com certificate, absent a built‑in IDE option?
visualstudio