Cannot use Client Certificate Authentication in .http files

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

I would like to ask for dfferent types of authentication support for HTTP files.

Currently it is possible to specify a token in the Authorization header but Client certificate authentication is not possible via http files. Therefore, we have to use Postman or other tools for testing such APIs.

---

Original Comments

Feedback Bot on 11/19/2024, 04:16 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[ViktorHofer]

This is asking about a new feature / API in networking hence I moved this to GitHub. @dotnet/ncl PTAL

[rzikm]

If it is the same .http files as in this article https://learn.microsoft.com/en-us/aspnet/core/test/http-files?view=aspnetcore-9.0, then this is probably not the right repository and the team working on the .http file editor should be better audience for this.

Note that the mentioned website explicitly calls out that certificate auth and many other features are unsupported in the Visual Studio .http editor, but are supported in VS Code's REST Client extension.

[mkArtakMSFT]

@captainsafia who do you think this issue should go to?

[halter73]

This is documented as currently unsupported, so this is more of a VS feature request than a bug:

Unsupported syntax

...

• Certificate based authentication

https://learn.microsoft.com/en-us/aspnet/core/test/http-files?view=aspnetcore-9.0#unsupported-syntax

[mkArtakMSFT]

I've reopened the original VS Feedback ticket and pinged @sayedihashimi to help with routing. Closing this as external.