Bug 1160380 - ssl on custom domain port 8443 incorrect certificate
Summary: ssl on custom domain port 8443 incorrect certificate
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.x
Assignee: Andy Goldstein
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-04 16:29 UTC by pepe
Modified: 2018-12-09 19:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-10 21:50:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.