Bug 1015178

Summary:	[RFE] Add katello CA certificate to system's local trust store in certs rpm
Product:	Red Hat Satellite	Reporter:	Marek Hulan <mhulan>
Component:	Installer	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Nightly	CC:	bkearney, stbenjam
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-11 18:28:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Marek Hulan 2013-10-03 15:00:06 UTC

Description of problem:

Bootstrap RPM with CA certificate does not install it in system storage (/etc/pki/tls/certs). It would be nice to have such ability so people could install this RPM so they would be able to use hammer CLI from another machines. Without this, default certificate is not trusted and we can not authenticate the server. Or there may be created another RPM for this purpose (this may configure goferd)

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1. Install bootstrap RPM that contains certificate
2. Navigate to Sat6 in browser

Actual results:

SSL error appears

Expected results:

No SSL error should appear

Additional info:

Comment 1 RHEL Program Management 2013-10-03 15:05:50 UTC

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 5 Stephen Benjamin 2016-07-29 14:21:51 UTC

Created redmine issue http://projects.theforeman.org/issues/15899 from this bug

Comment 6 Bryan Kearney 2016-08-11 18:28:04 UTC

We believe this was delivered with Satellite 6.2 or before. If you are still seeing this issue, please feel free to re-open with additional information.