Bug 1303176 – Installation/configuration limited to non-root users for auditing purposes

Bug 1303176 - Installation/configuration limited to non-root users for auditing purposes

Summary:	Installation/configuration limited to non-root users for auditing purposes

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	pki-core (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	7.3
Assigned To:	Matthew Harmsen
QA Contact:	Asha Akkiangady
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-01-29 13:46 EST by Matthew Harmsen
Modified:	2016-06-15 14:09 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-06-15 14:09:49 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Matthew Harmsen 2016-01-29 13:46:22 EST

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/pki/ticket/1483

 For auditing purposes, what I'd expect the installation to work (and what should be tested) is for a non-root user to be able to run pkispawn and install successfully.  After installation completion, only the installation user has access to his/her admin pkcs12.
Same with starting/restarting the server.

It could be just some sudo configuration that narrow down sudo so that some are allowed only to install/start/restart pki servers, and then another to edit pki instance configurations.

Comment 2 Nathan Kinder 2016-06-15 14:09:49 EDT

There is really nothing to fix here.  Installation of RHCS requires root permission (direct or via sudo).  Using sudo should work just fine, but that is a procedural/system issue and not a code issue that requires a bug.

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