Bug 1629624

Summary: router extended validation rejects EC private keys
Product: OpenShift Container Platform Reporter: Borja Aranda <farandac>
Component: NetworkingAssignee: Dan Mace <dmace>
Networking sub component: router QA Contact: zhaozhanqi <zzhao>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, bbennett
Version: 3.9.0   
Target Milestone: ---   
Target Release: 4.3.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-10-11 16:02:42 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 Borja Aranda 2018-09-17 08:21:18 UTC
Description of problem:
The router process rejects EC PRIVATE KEY with the format:

~~~
-----BEGIN EC PRIVATE KEY-----
           ...
-----END EC PRIVATE KEY-----
~~~

This is because this format is not contemplated in:
https://github.com/openshift/origin/blob/master/pkg/route/controller/routeapihelpers/validation.go#L80-L92

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

How reproducible:
Always

Steps to Reproduce:
1. Create a route with an EC PRIVATE KEY and cert in a router with extended validation enabled (it's enabled by default)

Comment 2 Dan Mace 2018-10-08 15:02:05 UTC
Moving this out to 4.x; we're unable to commit to a change in 3.11.

Comment 3 Dan Mace 2019-10-11 16:02:42 UTC
We ended up fixing this in 1723400 and didn't realize this bug precedes 1723400. Since we actually worked 1723400, I'm going to close this bug as a duplicate of the newer bug. I hope that makes sense!

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