Resolving “Site Is Not Trusted” or “Not Secure” Warnings for Locally Hosted Microix Application

Overview

When Microix Workflow Modules is hosted on your organization's local Microsoft IIS server, users may receive a browser message indicating that the website is Not Secure, Not Trusted, or that the site's security certificate cannot be verified.

These messages are related to the configuration of the organization's IIS server, SSL/TLS certificate, DNS, network, or client security policies rather than the Microix application.

Your organization's network or system administrator should review and resolve these warnings before the site is made available to users.

General Requirements

The IIS Server website should be configured so that users can access it through HTTPS without receiving browser certificate or security warnings.

At a minimum, your administrator should verify that:

• The website is accessed using HTTPS.
• A valid SSL/TLS certificate is assigned to the website.
• The certificate is not expired.
• The certificate matches the hostname/URL being used to access website that is hosting the Microix Application.
• The certificate and its certificate chain are trusted by the computers and devices accessing the site.
• IIS is properly configured to use the appropriate certificate.
• DNS is properly configured for the hostname used to access Microix.

Browsers normally validate the certificate's validity period, hostname, and issuing Certificate Authority. A failure in one of these areas can result in a browser security warning.

LAN-Only Environments

If Microix is available only from within your organization's local network (LAN), your administrator may use your organization's internal certificate infrastructure.

For example, organizations with an internal Certificate Authority (CA) can issue a certificate for the Microix IIS website and ensure that the appropriate certificate authority is trusted by all computers that access Microix.

If a self-signed or privately issued certificate is used, the organization is responsible for ensuring that the certificate is trusted by all applicable client computers and devices. Self-signed certificates are not automatically trusted by client devices.

Internet/WAN-Accessible Environments

If Microix is accessible from the Internet or outside the organization's LAN, Microix recommends using a valid certificate issued by a publicly trusted Certificate Authority.

The organization's administrator is responsible for appropriately configuring and securing Internet access to the locally hosted IIS server, including:

• Public DNS
• SSL/TLS certificates
• Firewalls and network routing
• HTTPS access
• Internet-facing IIS security
• Certificate renewal
• Any reverse proxy, VPN, WAF, or other network security technologies used by the organization

The externally accessible URL should match the hostname contained in the website's certificate.

Customer Responsibility

For locally hosted installations, the customer is responsible for maintaining and securing the environment used to host the Microix Application, including:

Microsoft IIS, Windows Server, DNS, SSL/TLS certificates, certificate trust and renewal, firewall/network configuration, and Internet/WAN exposure.

Microix Support can assist with issues related to the Microix application, but administration and troubleshooting of the customer's IIS, certificate infrastructure, DNS, firewall, and network environment should be performed by the customer's network/system administrator.

For any questions related to this article you may contact our support at modern@microix.net.