asp.net web api - ssl with webapi published using IIS. chrome warning - connection not secure due to self signed -


i trying use ssl webapi published using iis.

i've enabled ssl in webapi project setting ssl enabled true. on local pc i've created self signed certificate, gets issued mypcnamehere/mycompanydomainhere. (not sure if matters)

now if browse webpage in chrome/mozilla warning... connection not secure. mozilla's error certificate not trusted because self signed.

what options here handling this? (when warning connection not secure? or purely warning certificate self signed?)

i don't mind getting third party certificate, when tried wanted me verify own domain. mypc/mydomain inside company firewall don't see how obtain certificate.

any suggestions?

you error (warning actually) because you're using self signed certificate, browser doesn't recognize.

your options are:

  • obtain certificate issued trusted provider (the root certificate of issuer present in trusted root certificates store of browser/system
  • make browser trust self signed certificate (here's guide chrome, didn't find mozilla - have add permanent exception)

now, if you're using test, can browser trust self signed certificate.

if you're in company network, , have resources, might consider setting local ca, may use issue certificates testing machines on intranet, or dev environment. of course deploy root certificate on machines' trusted certificate store.

if you're going live (production machine accessible on internet), have consider provider.


Comments

Popular posts from this blog

python - How to insert QWidgets in the middle of a Layout? -

python - serve multiple gunicorn django instances under nginx ubuntu -

module - Prestashop displayPaymentReturn hook url -