Bug 1456471 - [RFE] Using own certifications for installer (CA, private key)
Summary: [RFE] Using own certifications for installer (CA, private key)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Installation
Version: 2.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukáš Hellebrandt
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: spacewalk-rfe space28
TreeView+ depends on / blocked
 
Reported: 2017-05-29 12:57 UTC by Pavel Studeník
Modified: 2018-04-20 12:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-20 12:32:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Pavel Studeník 2017-05-29 12:57:34 UTC
Description of problem:
Installer for Satellite 5 generates always new private key for SSL communication and I would like to use own created certs (CA and private key). Because my browser and systems have imported  own CA.

Version-Release number of selected component (if applicable):
spacewalk-setup-2.5.1-21.el6sat.noarch

How reproducible:
always


Steps to Reproduce:
1. copy own private key and CA to /root/ssl-build
2. run spacewalk-setup
3. own certs are used for services (maybe with some option)

Actual results:
Installer create new private key and new certs when old existed

Expected results:
It possible to use own certs for installation

Comment 1 Lukáš Hellebrandt 2017-09-11 13:39:52 UTC
PR: https://github.com/spacewalkproject/spacewalk/pull/570

Comment 2 Eric Herget 2017-12-14 13:41:54 UTC
spacewalk.git:
d130adc54ca99f5523a4f2d544953d0a6c84cdc8
7b79924a2a825df7f4680769a9e53a877e4072e8

Comment 3 Jiří Dostál 2018-03-26 12:17:02 UTC
Moving ON_QA

Comment 4 Jiří Dostál 2018-04-20 12:32:18 UTC
Spacewalk 2.8 has been released.
https://github.com/spacewalkproject/spacewalk/wiki/ReleaseNotes28


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