Bug 44514 – Chrome 58: NET::ERR_CERT_COMMON_NAME_INVALID

Bug 44514 - Chrome 58: NET::ERR_CERT_COMMON_NAME_INVALID


Summary:	Chrome 58: NET::ERR_CERT_COMMON_NAME_INVALID

Status:	RESOLVED DUPLICATE of bug 44312

Product:	UCS
Classification:	Unclassified
Component:	SSL
Version:	UCS 4.1
Hardware:	amd64 All

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-05-02 16:08 CEST by Michael Salm
Modified:	2017-05-02 16:12 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	5: Will affect all installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.286
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Chrome error page (177.35 KB, image/png) 2017-05-02 16:08 CEST, Michael Salm	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Salm 2017-05-02 16:08:27 CEST

Created attachment 8816 [details]
Chrome error page

When opening the UMC using HTTPS with Chrome 58 (probably Firefox 48, too) on Windows you get an error page complaining that it is not a secure site and the error message "NET::ERR_CERT_COMMON_NAME_INVALID".

Researches led me to these sites:
https://community.sophos.com/products/unified-threat-management/f/general-discussion/91085/https-scanning-web-protection-ssl-error-err_cert_common_name_invalid/#pi2132219853filter=answers
(This site provides a workaround using Windows GPO.)

http://stackoverflow.com/questions/27294589/creating-self-signed-certificate-for-domain-and-subdomains-neterr-cert-commo
(This site explains the ssl option "subjectAltName" used as workaround.)

Comment 1 Daniel Tröder

2017-05-02 16:12:12 CEST


*** This bug has been marked as a duplicate of bug 44312 ***