0

We have some Hosted Windows Services using net core (3.1 and later) and a self signed Certificates that we ship to customers.

These Services run on local servers and are listening on localhost:someports and have mostly rest Apis so the certificates are no problem on that side because we can validate them via code.

But some of them will get customer facing Status Frontend Uis where the browser will show the big "self signed certificate is bad" message which the user has to accept and don't look that nice overall.

So is it possible to use a "real" certificate for such services to use https without that hassle?

Mr.Pearce
  • 45
  • 1
  • 8
  • What does `"real"` mean? A certificate signed by a proper certificate authority? If so, I don't see why not - shouldn't be much different from what you've already done. – Xerillio Jun 08 '21 at 09:24
  • @Xerillio yes thats what i meant. Arent thoose bound to whatever "www.url.com" they are registered to? – Mr.Pearce Jun 08 '21 at 10:02
  • Yes, it's typically registered to a domain (often without a subdomain I believe - so not the "www" part in your example but a "*" instead). You can also use it for multiple domains just like StackExchange does for its sites - take a look at the certificate in your browser and look under "Subject Alt Names". You'll also see it's the same certificate used both on SO and e.g. https://superuser.com/ if you go there. – Xerillio Jun 08 '21 at 19:06

0 Answers0