Bug 733420

Summary:	User permission check missing for CryptoKeysHandler
Product:	Red Hat Satellite 5	Reporter:	Tomas Lestach <tlestach>
Component:	API	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Minar <mminar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	540	CC:	cperry, mkoci, mminar, tkasparek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-01 21:56:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	924232

Description Tomas Lestach 2011-08-25 16:43:00 UTC

Description of problem:
Nowadays any user may create or delete keys using the kickstart.keys APIs.

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

How reproducible:
always

Steps to Reproduce:
1. Create a simple satellite user.
2. Try to create and delete a GPG a/o SSL key using kickstart.keys API
  
Actual results:
Passed.

Expected results:
Only an org or config admin shall be able to modify GPG/SSL keys (at least there's such restriction in WebUI)

Comment 1 Tomas Lestach 2011-08-25 17:48:27 UTC

Tomas, please fix also cases, when specifying invalid description for delete and getDetails (NoSuchCryptoKeyException)

Comment 2 Tomáš Kašpárek 2012-08-28 11:58:27 UTC

fixed in spacewalk master 1dae339f2c4ef314436bddc3bf9364dbf526bacd

Comment 5 Clifford Perry 2013-10-01 21:56:42 UTC

Satellite 5.6 has been released. This bug was tracked under the release.  

This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly
before release). 

Moving to CLOSED CURRENT_RELEASE. 

Text from Upgrade Erratum follows:

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1395.html