Bug 1885442

Summary:	Console doesn't load in iOS Safari when using self-signed certificates
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Management Console	Assignee:	Rastislav Wagner <rawagner>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	aos-bugs, jokerman, spadgett, yapei
Target Milestone:	---
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-21 13:23:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1885343
Bug Blocks:

Description OpenShift BugZilla Robot 2020-10-06 01:51:56 UTC

+++ This bug was initially created as a clone of Bug #1885343 +++

If iOS Safari does not trust the console certificate, it blocks WebSockets. This causes console to only show a white screen since we rely on WebSockets for API discovery using GraphQL.

Comment 6 Yadan Pei 2020-12-17 06:50:34 UTC

Follow the steps in https://docs.openshift.com/container-platform/4.6/networking/ingress-operator.html#nw-ingress-setting-a-custom-default-certificate_configuring-ingress and https://docs.openshift.com/container-platform/4.6/networking/configuring-a-custom-pki.html#configuring-a-custom-pki to set customized certificates for web console, then visit console in iPhone 11 Safari, web console can be loaded successfully instead if blank page


Verified on 4.6.0-0.nightly-2020-12-16-201440

Comment 8 errata-xmlrpc 2020-12-21 13:23:55 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.6.9 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:5614