Back to bug 1310266
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Rory Thrasher | 2016-02-22 20:30:19 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | rubygem-openshift-origin-node-1.38.5.2-1.el6op rubygem-openshift-origin-console-1.35.5.1-1.el6op rubygem-openshift-origin-frontend-apache-vhost-0.13.1-1.el6op | |||
| errata-xmlrpc | 2016-02-22 20:30:50 UTC | Status | MODIFIED | ON_QA |
| weiwei jiang | 2016-02-26 06:13:48 UTC | Status | ON_QA | VERIFIED |
| Sally | 2016-03-10 20:02:49 UTC | Doc Text | Cause: Web-console used to have an intermediate 'Certificate Chain' field. The cert files were then internally concatenated. SSL certificate providers often issue a 'fullchain.pem' file (or similar) that was confusing to users who didn't know whether to use this file or the non-concatenated files. Finally, the rhc tool to upload SSL certs does not include an 'cert chain' option, when using the rhc tool users have always been required to supply concatenated cert file. Consequence: Users were getting a 'B rating' and/or 'chain incomplete' warning unless they used the 'fullchain.pem' file. Fix: Removed SSL Certificate Chain Field from web console. Documented that the user must concatenate SSL cert files into a single file to upload, or upload the already-concatenated file included in the SSL certificate from the SSL certificate provider. Also documented how users should manually concatenate the cert files if the SSL cert provider did not provide a concatenated file. Result: rhc tool now matches web console. Uploading SSL certs process has been clarified for users. |
|
| errata-xmlrpc | 2016-03-17 17:01:45 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-03-22 16:54:58 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-03-22 12:54:58 UTC |
Back to bug 1310266