Bug 1160380

Summary: ssl on custom domain port 8443 incorrect certificate
Product: OpenShift Online Reporter: pepe <andreas>
Component: ContainersAssignee: Andy Goldstein <agoldste>
Status: CLOSED UPSTREAM QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: agoldste, jialiu, jokerman, lmeyer, mmccomas
Target Milestone: ---   
Target Release: 2.x   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-10 21:50:57 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 pepe 2014-11-04 16:29:04 UTC 
after uploading the certificate for my openshift node gear i can access the url via https without any problem. 
when i try to access it via port 8443 i get an invalid certificate.

in chrome for example i get:

This server could not prove that it is api.2.myapp.com; its security certificate is from *.rhcloud.com. This may be cause by a misconfiguration or an attacker intercepting your connection.

it seems like openshift is serving the wrong certificate for port 8443
Comment 1 Andy Goldstein 2014-11-10 21:50:57 UTC 
Custom SSL certificates for the websocket proxy are not currently supported. Created the following upstream feature request:

https://trello.com/c/EzMdQCQn/571-add-per-app-ssl-certificate-support-to-the-nodejs-websocket-frontend-plugin