Page tree
Skip to end of metadata
Go to start of metadata

Last updated: Apr 11, 2019 22:07

Problem

Security Certificate is not accepted by Chrome browser despite being installed and trusted on Web VM.

Solution

The problem is caused by the changes introduced in Chrome browser versions 58+.

New Certificate should be created according to these guidelines:

Chrome 58+ no longer matches the Common Name (CN) in certificates, it uses Subject Alternative Names (SAN) instead.

SAN must contain proper DNS or IP entry.

When DNS is used, it should be a resolvable FQDN name.

When an IP address is used, it should be explicitly specified as such within the SAN chain.


Chrome 58+ no longer matches the Common Name (CN) in certs.

Now it uses Subject Alternative Names (SAN) instead.

SAN must contain proper DNS or IP entry.

When DNS is used, it should be a resolvable FQDN name.

When an IP address is used, it should be explicitly specified as such within the SAN chain.