After upgrading to MTC-M 14.1.2 and setting up SSL access using self-signed certificates (USS Files - TrustStore), the following error is received in the Chrome browser when trying to connect to MTC-M:
After receiving this error, clicking the 'Advanced' button allows the connection to be made; however, the connection is not secure (i.e., HTTP versus HTTPS).
How can this be fixed?
Release : 14.1
Self-signed certificates are not supported in MTC-M.
When the message "NET::ERR_CERT_AUTHORITY_INVALID" appears when trying to connect to the MTC-M HTTPS address, it is possible to still proceed to the target webpage (such as by clicking the 'Advanced' button). This message is issued as a result of the browser not supporting Self-Signed Certificates. Today it is not possible for Vantage to bypass this error (but in the past this was possible by importing such certificates and using them as being valid). The only way to avoid this situation is to use a certificate from a valid authority, and not use self-signed certificates. To implement this change to avoid these issues it is recommended to store certificates in a SAF Keyring. Further documentation on this setup using a SAF keyring can be found here. ((Recommended) Enable HTTPS with Certificates Stored in SAF Keyring)