Bug 1473658 - Documentation does not describe how to create a RHUI certificate.
Documentation does not describe how to create a RHUI certificate.
Status: CLOSED CURRENTRELEASE
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: Documentation (Show other bugs)
3.0.0
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Les Williams
Radek Bíba
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-21 07:57 EDT by James Read
Modified: 2017-10-06 09:22 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-10-06 09:22:06 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description James Read 2017-07-21 07:57:36 EDT
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Update_Infrastructure/2.1/html/Administration_Guide/chap-Red_Hat_Update_Infrastructure-Administration_Guide-Managing_Entitlement_Certificates.html

Section Number and Name: 5.x

Describe the issue: 

No description of where to get updated certificates from. It would be good to link to the certificate creation area on the customer portal; https://access.redhat.com/management/consumers?type=rhui

Suggestions for improvement: ^^

Additional information: CCSPs often find this confusing.
Comment 3 James Read 2017-07-21 11:39:24 EDT
Ah, for RHUI 3, this *is* documented in 4.6; https://access.redhat.com/documentation/en-us/red_hat_update_infrastructure/3.0/html/system_administrators_guide/registration_and_subscriptions#download_entitlement_certificate

However, I think this section could be significantly enhanced with just a couple of screenshots. Could I change this meaning of this bug to be "improve documentation for getting an enablement sub - add screenshots? :)"

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