Bug 1573487

Summary:	IE11 and Console CORS problem
Product:	OpenShift Container Platform	Reporter:	Eric Paris <eparis>
Component:	Management Console	Assignee:	Samuel Padgett <spadgett>
Status:	CLOSED WONTFIX	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.9.0	CC:	aos-bugs, jforrest, jokerman, mmccomas
Target Milestone:	---
Target Release:	4.1.0
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:	2019-06-04 20:12:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eric Paris 2018-05-01 13:40:34 UTC

Today openshift adds the console/api TLS cert onto the amazon ELB which fronts the console/api machines. I'm told (through the grapevine which no one really knows the truth of) that this is because of some "IE11 CORS bug." But I know little else.

It might be this issue:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/1282036/
(It might not, I really don't know)

I would like to stop loading the cert into the ELB. This makes cert management much harder. If this can be fixed in the console I would very strongly like to fix it there.

Comment 3 Samuel Padgett 2019-06-04 20:12:36 UTC

This is no longer an issue in 4.1 since the console uses a proxy and does not rely on CORS. We've also dropped support for IE 11 in 4.1. We have no plan to change this in the 3.x console.