Bug 339121

Summary:	Permission Error for SDC Kickstart Tab
Product:	[Retired] Red Hat Network	Reporter:	Máirín Duffy <duffy>
Component:	RHN/Web Site	Assignee:	Sebastian Skracic <sskracic>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	rhn500	CC:	bkearney, rhn-bugs, tao
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	https://rhn.webqa.redhat.com/rhn/systems/details/kickstart/ScheduleWizard.do?sid=1007659714
Whiteboard:	US=28874
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-09-25 13:03:13 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:	450300

Description Máirín Duffy 2007-10-19 03:47:36 UTC

Description of problem:

https://rhn.webqa.redhat.com/rhn/systems/details/kickstart/ScheduleWizard.do?sid=1007659714

This isn't an issue for org admins. But it is an issue for system group admins.
Here are the steps to reproduce:

1) log into a corporate account as an org admin.
2) create a non org admin user.
3) create a system group.
4) add your non org admin user to the system group as an admin in the admin tab.
5) add a system with provisioning entitlements to the system group.
6) log out as org admin. log in as your newly-created non-org admin group admin.
7) go to the system you added to the system group.
8) click on the provisioning tab. you'll get a permission error. 

How reproducible:

Very. More details in a private comment following this.

Comment 2 Máirín Duffy 2007-10-19 17:08:37 UTC

Forgot to mention, this bug does not affect Satellite only hosted.

Comment 3 Grant Gainey 2008-06-04 18:30:51 UTC

OK - this happens because the action's security currently requires the user to
be a config-admin to access provisioning.  That doesn't make a lot of sense in
this context, and so that protection should be removed.

Workaround is to give the user config-admin - although that may give that user
more access than the customer wants.

Comment 4 Sebastian Skracic 2008-06-24 13:08:05 UTC

Fixed in r118829.