Bug 1045577

Summary: 6.8.6.1. Creating a Matching Certificate (OSE 1.2 docs)
Product: OpenShift Container Platform Reporter: Luke Meyer <lmeyer>
Component: DocumentationAssignee: brice <bfallonf>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.2.1CC: alyoung, jokerman, libra-onpremise-devel, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 22146, Deployment Guide-1-1.2 Build Date: 26-11-2013 14:18:45 Topic ID: 20615-477529 [Specified]
Last Closed: 2014-01-08 23:43:11 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 Luke Meyer 2013-12-20 18:34:53 UTC
Title: Creating a Matching Certificate
https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/1/html-single/Deployment_Guide/index.html#sect-SSL_Certificates

Describe the issue:
The openssl command here is outright missing a line and will not work. Also there are some other adjustments needed.

Suggestions for improvement:
It should read like the OSE 2.0 docs at https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#sect-SSL_Certificates

Comment 1 Luke Meyer 2013-12-20 18:44:56 UTC
Actually this and the 2.0 equivalent should read the same, but without the leading > marks:

---
# cat << EOF | openssl req -new -rand /dev/urandom \
  -newkey rsa:2048 -nodes -keyout /etc/pki/tls/private/localhost.key \
  -x509 -days 3650 \
  -out /etc/pki/tls/certs/localhost.crt 2> /dev/null
XX
SomeState
SomeCity
SomeOrganization
SomeOrganizationalUnit
*.$domain
root@$domain
EOF
---

Enables wholesale cut and paste. Granted, they may not want to cut and paste this as-is, but at least it will give them a cert with the right domain if they do.

Comment 3 brice 2013-12-23 00:53:39 UTC
Edited out the leading > marks, and made the topic for 2.0 and 1.2 match. Made sure the command matched the one in the initial comment above.

This all seems straight-forward. Unless you have anything else, Luke, I'm going to put this BZ onto QA.

Comment 5 Luke Meyer 2013-12-23 13:30:36 UTC
Looks good, thanks!