Blazor WebAssembly - certificate [Linux] [Ubuntu 20.20]

[przemo098]

Describe the bug

It's impossible to run secured connection in Linux environment.
As far as I'm able to generate self signed CA certificate which works for ASP.NET core:

1. Using $ dotnet dev-certs https --clean --import localhost.pfx -p 1234
   results with:

- The certificate at 'localhost.pfx' is not a valid ASP.NET Core HTTPS development certificate.

There is no place to put it in Blazor WebAssembly configuration (appsettings).

To Reproduce

Install Ubuntu 20.20
Install .NET 5
dotnet new blazorwasm
dotnet run

• connection is not secured
• generate certificate with openssl => no place to attach it in configuration

Further technical details

• The IDE (VS Code) 1.51

P.S.
I tried to debug Blazor WASM in VS code it's also impossible.
I guess certificate issue might be the reason, yesterday I received some weird wrong certificate outputs which I'm unable to reproduce today after all day battle...
Also I was unable to debug Blazor WASM in Windows env, however after certificate installation debugger started to work...

[mkArtakMSFT]

Thanks for contacting us.
I believe dotnet devcerts doesn't support cert generation for Linux yet. I think that is tracked here: #7246.
@javiercn can you please confirm this? Thanks!

[przemo098]

Yes I know that devcerts doesn't support that however they generate certificated but the wrong one..., I want to import certs generated by me. Is there any manual way to do that? Best regards Przemysław Kamiński

…

________________________________ From: Artak <notifications@github.com> Sent: Monday, November 30, 2020 6:41:42 AM To: dotnet/aspnetcore <aspnetcore@noreply.github.com> Cc: Przemysław Kamiński <przemo098@hotmail.com>; Author <author@noreply.github.com> Subject: Re: [dotnet/aspnetcore] Blazor WebAssembly - certificate [Linux] [Ubuntu 20.20] (#28237) Thanks for contacting us. I believe dotnet devcerts doesn't support cert generation for Linux yet. I think that is tracked here: #7246<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Faspnetcore%2Fissues%2F7246&data=04%7C01%7C%7C4203ec6ad3a54c9282de08d894f29e0d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637423117032997418%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=w8XuIVyvDRKFSg9FhzLCzCIpkCWSYOWuKCwChUf2vIk%3D&reserved=0>. @javiercn<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjaviercn&data=04%7C01%7C%7C4203ec6ad3a54c9282de08d894f29e0d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637423117033012393%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mTqeK1bS2N6k%2Fs20YQAicL8lE6n1u84T5X7LU7LX05k%3D&reserved=0> can you please confirm this? Thanks! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Faspnetcore%2Fissues%2F28237%23issuecomment-735559740&data=04%7C01%7C%7C4203ec6ad3a54c9282de08d894f29e0d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637423117033027366%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fxdBSsJw80eMdMcJeIz9%2F7XtcNo9%2Bm050gLhGisIafU%3D&reserved=0>, or unsubscribe<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABP5X76KNAL4BQMQYCI436DSSMWBNANCNFSM4UGX23DQ&data=04%7C01%7C%7C4203ec6ad3a54c9282de08d894f29e0d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637423117033037350%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=GAvQVLvRSs3IIYU8U%2Ff7mAK%2BxAvIueM66gAkIMc2aAw%3D&reserved=0>.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[aloh86]

I am needing to do the same as @przemo098. On Fedora 33, trying to debug Blazor WASM project in VSCode. According to this thread: #21166, it seems that dev-certs needs to be trusted. However, since Linux users cannot do this, we need to supply our own self-signed-certs. How do we tell the WASM project to use the .pfx file that we generated using OpenSSL?

[przemo098]

I think you can try to create Blazor WASM hosted in another project by Kestrel but I didn't tried it. I know that VS can generate solution with 2 projects. Later on appsetings.json in second project can be modified to handle your custom .pfx Best regards Przemysław Kamiński

…

________________________________ From: Alex Oh <notifications@github.com> Sent: Wednesday, December 16, 2020 5:06:11 AM To: dotnet/aspnetcore <aspnetcore@noreply.github.com> Cc: Przemysław Kamiński <przemo098@hotmail.com>; Mention <mention@noreply.github.com> Subject: Re: [dotnet/aspnetcore] Blazor WebAssembly - certificate [Linux] [Ubuntu 20.20] (#28237) I am needing to do the same as @przemo098<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fprzemo098&data=04%7C01%7C%7C0cbf3861e1114b6b216608d8a177ec66%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637436883728696701%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Dnnu%2FRaPOKS%2Bmd8Yejh4gzuqzCTEvb01TopjU6j5Jdc%3D&reserved=0>. On Fedora 33, trying to debug Blazor WASM project in VSCode. According to this thread: #21166<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Faspnetcore%2Fissues%2F21166&data=04%7C01%7C%7C0cbf3861e1114b6b216608d8a177ec66%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637436883728706688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TyWTi4worso8QPHxT%2FQQQthfPkkFK8Tp8g0Eawh1M7k%3D&reserved=0>, it seems that dev-certs needs to be trusted. However, since Linux users cannot do this, we need to supply our own self-signed-certs. How do we tell the WASM project to use the .pfx file that we generated using OpenSSL? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Faspnetcore%2Fissues%2F28237%23issuecomment-745750095&data=04%7C01%7C%7C0cbf3861e1114b6b216608d8a177ec66%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637436883728706688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=rMXzo3MUnon%2B0PUVRIiAbC18gPmNZ1LWFEbTJZ9rJs8%3D&reserved=0>, or unsubscribe<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABP5X72KMQDRH2T2KTU5B23SVAW3HANCNFSM4UGX23DQ&data=04%7C01%7C%7C0cbf3861e1114b6b216608d8a177ec66%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637436883728716690%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8iemEc%2Fr30XWe156JPDJWe%2BML7PL3Qtoxr2wJBkbiHM%3D&reserved=0>.

[javiercn]

A few things to point out:

• As @mkArtakMSFT points out, there is no support for trusting certificates on Linux through the dev-certs tool.
• The --import flag of the dotnet dev-certs tool is not mean to be a general purpose tool for importing certificates, it's only meant to work with certificates generated by the dotnet dev-certs tool.
• You should be able to use your own certificate with the devserver by specifying the path and password as command-line arguments following the standard asp.net config format or within a json file named blazor-devserversettings.json

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.