How do you use cloud databases? Take the survey.

HTTPS for SQL Monitor using a self-signed certificate

Due to some strange AD related issues, I have been asked to try using Open ID authentication for SQL Monitor. This requires using HTTPS instead of HTTP.

I have created a self-signed certificate, installed it and put it under the "Trusted Root Certificate Authorities" on the machine hosting the web service.

I updated the kestrel config file accordingly.

<?xml version="1.0" encoding="utf-8"?>
<configuration>

  <kestrel>
    <endpoints>
      <http>
        <url>http://*:8080</url&gt;
      </http>
      <https>
        <url>https://*:30443</url&gt;

        <certificate>
          <path>C:/Install/certs/wild.fpc.local-2023-03-07-095823.p12</path>
  <password>replaced_password</password>
        </certificate>
      </https>

    </endpoints>
  </kestrel>
</configuration>

But when trying to access the page, I get a NET:ERR_CERT_AUTHORITY_INVALID error in MS EDGE. Looking at the Certificate in EDGE it states that "This CA Root certificate is not trusted. To enable trust, install this certificate in the Trusted Root Certification Authorities store" - but I thought I already did that in certmgr. Is there somewhere else that I need to install it than the server hosting the web service?

In Chrome, I can ignore the error and proceed to the webpage which works as usual (except for the "Not secure" bit at the top of the browser).
Tagged:

Answers

Sign In or Register to comment.