Bug 795905 - Split Debug Certificate "Download" button into two buttons: "Generate" and "Download"
Summary: Split Debug Certificate "Download" button into two buttons: "Generate" and "D...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-21 19:06 UTC by james labocki
Modified: 2014-03-18 17:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-18 17:37:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


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