Aspnetcore.docs: Firefox does not trust self-signed certificates (dot net core development)

[jaoord]

Even after cleaning old certificates and creating new certificates and restarting the browser, Firefox will not trust the localhost development certificate:

How can we run a localhost dotnet development project in Firefox?

---

Documentdetails

⚠ Dit gedeelte niet bewerken. Het is vereist om problemen te koppelen tussen docs.microsoft.com en GitHub.

• ID: c7ddfb2f-5dea-5e31-2a27-02a4dc16104c
• Version Independent ID: 12ca0b9a-2638-a4ce-c45f-d4579c83dafb
• Content: Enforce HTTPS in ASP.NET Core
• Content Source: aspnetcore/security/enforcing-ssl.md
• Product: aspnet-core
• Technology: aspnetcore-security
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[Rick-Anderson]

Needs to be fixed

[Rick-Anderson]

@jaoord see https://github.com/dotnet/AspNetCore.Docs/pull/20356

[guardrex]

@jaoord ... I use FF, including with 5.0 preview, and I'm not seeing any cert errors.

We probably can't provide product support here for that, so you can open an issue for the product unit to see if they want to investigate the cause. Before doing that tho, I recommend that you search the Net, particularly SO, first just to make sure that someone hasn't already called it out and figured out the cause. Then ... open an issue here ...

https://github.com/dotnet/aspnetcore/issues

If you do find out what's causing it and think that docs need to mention a gotcha, then you can post back on this issue (or open a new one) with what you find out.

@Rick-Anderson I recommend closing this for now until more information is available.

[jaoord]

As mentioned in the other issue (#20356) the solution is to go to about:config in Firefox and set security.enterprise_roots.enabled to true.

[guardrex]

Very good ... glad it had a happy ending. That's the default for that setting, so I don't think we need doc coverage. Thanks for letting us know how it turned out.