Bug 1471155

Summary: clarify route CA certifiate edit field
Product: OpenShift Container Platform Reporter: Aleksandar Kostadinov <akostadi>
Component: Management ConsoleAssignee: Jessica Forrester <jforrest>
Status: CLOSED ERRATA QA Contact: XiaochuanWang <xiaocwan>
Severity: low Docs Contact:
Priority: medium    
Version: 3.5.1CC: aos-bugs, jokerman, mmccomas, yapei
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Clarifies help text on the Route creation and editing pages to make it clear that the CA certificates should be certificate chains.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-28 22:01:28 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:
Description Flags
route edit page none

Description Aleksandar Kostadinov 2017-07-14 14:21:18 UTC
Created attachment 1298378 [details]
route edit page

Description of problem:
When you `edit` a route in management console to set custom certificate, one of the fields is labeled "The PEM format CA certificate". Another one is "The PEM format CA certificate to validate ...". 

I think these need to be changed to "certificate chain" to make clear that a full certificate chain should be given. That means:


Attaching a screenshot of the page.

Comment 1 openshift-github-bot 2017-11-03 16:00:20 UTC
Commits pushed to master at https://github.com/openshift/origin-web-console

Bug 1471155 - update help text on CA inputs

Merge pull request #2443 from jwforres/route-edit-ca-help

Automatic merge from submit-queue.

Bug 1471155 - update help text on CA inputs

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

Comment 4 Yadan Pei 2017-11-08 08:42:12 UTC
On v3.7.0-0.196.0

The help text for CA inputs changed to "CA certificate chain"


Comment 7 errata-xmlrpc 2017-11-28 22:01:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.