Bug 1715020

Summary:	OAuth object validation allows multiple IdPs being set within a single IdP object
Product:	OpenShift Container Platform	Reporter:	Standa Laznicka <slaznick>
Component:	apiserver-auth	Assignee:	Erica von Buelow <evb>
Status:	CLOSED ERRATA	QA Contact:	scheng
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, mkhan, sponnaga, xtian
Target Milestone:	---	Keywords:	OSE41z_next
Target Release:	4.1.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	4.1.2
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-19 06:45:34 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:
Bug Depends On:
Bug Blocks:	1718956

Description Standa Laznicka 2019-05-29 11:55:28 UTC

Description of problem:
When modifying the oauth/cluster object, user is allowed to specify multiple identity provider types within a single identity provider object (see example below)

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

How reproducible:
Always

Steps to Reproduce:
1. oc edit oauth cluster
2. the following is allowed in spec.identityProviders:
- name: misconfiguredIdP
  htpasswd:
    fileData:
      name: htpasswd-config
  basicAuth:
    uri: https://example.com
    tlcClientCert:
      name: mycert
    tlsClientKet:
      name: mykey

Actual results:
Successful edit

Expected results:
Validation refuses to create an IdP config like that

Comment 5 errata-xmlrpc 2019-06-19 06:45:34 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, 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/RHBA-2019:1382