Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1543308

Summary:	Prometheus oauth-proxy refuse connection if a custom CA is used on LoadBalancer
Product:	OpenShift Container Platform	Reporter:	Franck Grosjean <fgrosjea>
Component:	Hawkular	Assignee:	Paul Gier <pgier>
Status:	CLOSED DUPLICATE	QA Contact:	Junqi Zhao <juzhao>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	aos-bugs, fcami, jcantril
Target Milestone:	---
Target Release:	3.9.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-22 21:57:12 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 Franck Grosjean 2018-02-08 08:37:25 UTC

Description of problem:
Prometheus oauth-proxy refuses authentication with a custom CA

Version-Release number of selected component (if applicable):


How reproducible:
Configure Openshift with upstream load balancer and custom CA and cert
Deploy prometheus according to the documentation


Steps to Reproduce:
1. Install Openshift with load balancer for UI and API (Public URL)
2. Install custom CA on load balancer
3. Deploy prometheus with ansible according to documentation
4. Connect to prometheus using exposed route

Actual results:
Authentication failed

Expected results:
Authentiation should work 

Additional info:
Prometheus oauth proxy rejects connection if PublicURL use a different CA

Comment 2 Paul Gier 2018-02-22 21:57:12 UTC

I believe this is the same issue as 1535585

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