Bug 795905

Summary: Split Debug Certificate "Download" button into two buttons: "Generate" and "Download"
Product: Red Hat Satellite Reporter: james labocki <jlabocki>
Component: WebUIAssignee: Partha Aji <paji>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: mmccune
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-18 17:37:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description james labocki 2012-02-21 19:06:18 UTC 
Description of problem:
Under the Organization, List, Organization Details the "Download" button both generates and provides for download the ueber certificate. If a user accidentally presses this button it generates a new certificate which renders all template xml files useless (certificates no longer valid). This is not desirable.

Expected results:
Split "Download Certificate" button into two buttons: "Generate Certificate" and "Download Certificate". Have "Generate" option prompt for confirmation of the action.
Comment 1 Mike McCune 2012-02-21 20:11:49 UTC 
Actually if you download again it just uses the same cert and key.  I just did this:

1) Login -> Generate Certificate -> download to local file:

ACME_Corporation-key-cert.pem

2) Generate Certificate again -> download to new file:

ACME_Corporation-key-cert(2).pem

3) Note that the 2 files are identical:

$ md5sum *.pem
cc942316bbd6cd423c74c04f4e0ee117  ACME_Corporation-key-cert(2).pem
cc942316bbd6cd423c74c04f4e0ee117  ACME_Corporation-key-cert.pem

The API just re-sends you the same cert if one exists already.  

we should make the UI more clear about this but it should be workable as it stands today.
Comment 2 Mike McCune 2014-03-18 17:37:27 UTC 
This bug was closed because of a lack of activity.  If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.