Bug 713921 - Remove question from entitlement certificate generation
Summary: Remove question from entitlement certificate generation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: Documentation
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lana Brindley
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-16 19:11 UTC by Jay Dobies
Modified: 2016-02-18 05:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-29 04:51:09 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jay Dobies 2011-06-16 19:11:27 UTC
When generating an entitlement certificate, we no longer prompt the user to enter a serial number. We keep track and auto-increment them automagically.

Comment 1 Lana Brindley 2011-06-24 00:54:57 UTC
Removed the following step:
<step>
	<para>
		Enter the serial number of the certificate. This is a number that is assigned to each certificate by the certificate authority (CA). It must be unique for each certificate, and each CA:
	</para>
			 
<screen>
Serial number of the certificate [10]: <remark>Is 10 the default value? How does that work?</remark>
</screen>
</step>

Revision 1-14.

LKB

Comment 2 Sachin Ghai 2011-06-28 03:07:43 UTC
Verified in Install guide at:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/chap-Installation_Guide-Client_Entitlements.html

Under "Procedure 7.1. Generate an Entitlement Certificate" of "chapter 7 Client Entitlements", the question to "Enter the serial number of certificate" has now been removed.

Comment 3 Lana Brindley 2011-07-29 04:51:09 UTC
This book is now available at http://docs.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/index.html

Please raise a new bug for any further changes.

LKB


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