Bug 1479455 - [RFE][M-5] SSL certificate configuration menu in appliance console.
Summary: [RFE][M-5] SSL certificate configuration menu in appliance console.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.11.0
Assignee: Joe Vlcek
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On: 1581467
Blocks: 1511957
TreeView+ depends on / blocked
 
Reported: 2017-08-08 15:02 UTC by Gellert Kis
Modified: 2021-03-11 15:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
5.8
Last Closed: 2019-01-02 14:10:29 UTC
Category: Feature
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Joe Vlcek 2018-05-22 18:04:01 UTC
Just want to capture a conversation I had with Brad Ascar where he confirmed that
what this RFE is requesting is to add support to the appliance_console (ap) that
would expect the new SSL certs to be place on the appliance. The ap would prompt
for the file path to where the new certs could be found on the appliance and
configure them.

Also the ap could take the hostname or IP address of a different appliance that
already has the certificates installed and scp them to the local appliance and
configure them.


For example:

From the AP add an option:

  #x: Import new SSL certs

    1: from a file on this appliance?
       1.a enter the file path to the new SSL certs: [/tmp/new_ssl_certs]

    2: from an already configured appliance?
       2.a Enter the hostname or IP of a appliance to pull SSL certs from:
       2.b Enter the name of the certs to pull from appliance %{ans from 2.a}:

Comment 5 Joe Vlcek 2019-01-02 14:10:29 UTC
I am closing this RFE. The "value add" of implementing it seems minimal and the desire to have it
has been markedly reduced.

Please reopen with more justification if desired.


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