Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.
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.