Bug 1149901 - Proper SSL setup for custom domain
Summary: Proper SSL setup for custom domain
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Management Console
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Fabiano Franz
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks: 1152699
TreeView+ depends on / blocked
 
Reported: 2014-10-06 20:54 UTC by Jack
Modified: 2015-05-15 01:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1152699 (view as bug list)
Environment:
Last Closed: 2015-03-05 19:56:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jack 2014-10-06 20:54:39 UTC
Description of problem:
I have installed the SSL certificate and the Intermediate Certificate using the Management Console and while this appears to be working for Chrome and Safari, Firefox and IE are having issues and claim that it is an untrusted site.  I've raised this issue with the SSL provider SSL.com and they have given me new files to add to my site truthmapping.com which I have done yet the problem persists.  Their instructions are below but I can not do this directly as far as I'm aware.  How can I get this site working in Firefox and IE?

Their instructions:
The file should be saved to a secure location; /etc/ssl/certs or a similar directory and specified in the following directive in the Apache configuration file:

SSLCertificateChainFile /etc/ssl/certs/www_truthmapping_com.ca-bundle


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


How reproducible:
very

Steps to Reproduce:
1. Visit the site with Firefox.

2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fabiano Franz 2014-10-06 20:59:42 UTC
Please check if the workaround reported in the bug below helps:

https://bugzilla.redhat.com/show_bug.cgi?id=985952

We have another report on a similar issue that is under investigation at the moment:

https://bugzilla.redhat.com/show_bug.cgi?id=1147868

Comment 2 Jack 2014-10-06 21:10:20 UTC
I have combined those certs and submitted as one, then restarted the app.  I see no change.  Does this take some time?

Comment 3 Jack 2014-10-06 22:17:17 UTC
Still no luck.  More data:
http://www.ssltools.com/certificate_lookup/www.truthmapping.com

Comment 4 Jack 2014-10-07 00:16:18 UTC
Here is some contact info:

Jack,

I am confident that these new files should work. Please send them over and let us know if they have any problems with them. I have validated them using various tools to make sure they are correct.



Fred Newtz
SSL Sales & Support HelpdeskSSL Support Team
support
https://www.ssl.comSSL Support Team
support
http://www.ssl.com

Comment 5 Jack 2014-10-07 02:56:55 UTC
This site is 'untrusted' to many people.  Please advise.

Comment 6 Fabiano Franz 2014-10-07 20:57:45 UTC
A hotfix will be published soon. 

Please try the following workaround (involves 2 commands to be performed on a Linux or Mac terminal):

1. Combine the certificate and chain files into one:

cat www_truthmapping_com.crt DigiCertCA.crt > combined.pem

Notice the file names may vary, the first one is the website-specific certificate file and second is the chain file, as received from your certificate issuer. This will result in a combined certificate file named "combined.pem".

2. Set the combined certificate using rhc:

rhc alias update-cert <app_name> www.truthmapping.com --certificate combined.pem --private-key www.truthmapping.com.key

Where <app_name> is the name of your openshift application. Again the private key file name may vary. If your private key requires a password you need to add in the end: --passphrase <passphrase>

Let us know the results.

Comment 7 Jack 2014-10-07 21:29:06 UTC
Results:

> rhc alias update-cert live www.truthmapping.com --certificate combined.pem --private-key tmap.key 
Invalid private key or pass phrase: Could not parse PKey: no start line

Do I need another param for the pass phrase?

Comment 8 Jack 2014-10-07 21:32:33 UTC
Doh.  Just saw your last comment.  With passphrase I get:
SSL certificate successfully added.

I'm in.  Thank you!

Comment 9 Jack 2014-10-07 21:38:45 UTC
Hmm.  This still doesn't look good, no?
http://www.ssltools.com/certificate_lookup/www.truthmapping.com

Comment 10 openshift-github-bot 2014-10-07 22:21:55 UTC
Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/a475004bede3f2ed476cf8bcbad46a1cbac4a393
Bug 1149901 - add missing line break to certificate files

Comment 11 Fabiano Franz 2014-10-08 01:13:36 UTC
Yes, you are good now. I prefer https://www.digicert.com/help/ which gives you more detailed information. 

You can also open Firefox with a new profile to make sure you don't have any certificate history, then open your website to confirm it doesn't warn by invalid certificate (use 'firefox -ProfileManager' and create a new profile). 

A fix has been pushed to our repository and will be in openshift.com soon.

(In reply to Jack from comment #9)
> Hmm.  This still doesn't look good, no?
> http://www.ssltools.com/certificate_lookup/www.truthmapping.com

Comment 12 Fabiano Franz 2014-10-08 01:15:36 UTC
Fixed in https://github.com/openshift/origin-server/pull/5857

Comment 13 Jack 2014-10-08 02:26:54 UTC
I like the answer back from the digicert site better also.  ;)

Comment 14 Yujie Zhang 2014-10-08 08:35:16 UTC
Tested on devenv_5218, the ssl chain can be added successfully, so verify this bug, thanks.

Comment 15 amnesia7 2014-11-08 23:36:03 UTC
Has this been fixed on Openshift Online yet because when I try to follow the same instructions it says "SSL certificate successfully added." but Firefox is still saying:

www.mydomain.com uses an invalid security certificate. 
The certificate is not trusted because no issuer chain was provided. 
(Error code: sec_error_unknown_issuer)

I have done:

cat ssl.crt sub.class1.server.ca.pem > combined.pem

It is a StartSSL certificate - they suggested using the .pem file rather than the sub.class1.server.ca.crt which they said was DER encoded.

then:

rhc alias update-cert <app_name> www.mydomain.com --certificate combined.pem --private-key ssl.key --passphrase <passphrase>

but no joy.

Comment 16 amnesia7 2014-11-10 22:36:32 UTC
According to StartSSL guys:

"Apparently you are using a Apache - you have to configure it differently according to http://www.startssl.com/?app=21"

Is that correct or should the StartSSL certificate work anyway?

Comment 17 amnesia7 2014-11-11 19:13:06 UTC
Has something changed recently because it is now saying that the certificate is now correctly installed and looks to be ok when accessed via firefox on opensuse?

Or should it have taken a few days for the certificate to apply itself correctly after uploading it?


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